Tag Info

Hot answers tagged

2

The first virtual host directive is the default "catch all." Any unrecognized host names get handled by whichever virtual host directive comes first. The solution to your problem is to create a default virtual host directive that prints out an error. I have one that I use. I've previously posted it in this answer 404 Not Found -- Hostname Not ...


2

As you already said, you just have to wait. If you are 100% sure you setup your nameservers correctly and your registrar can confirm this, then you'll just have to wait. :-)


1

If your host takes care of the DNS when you've changed your nameservers, it should be fine. Changing the 'A' record in your control panel wouldn't have any effect because your nameservers don't point to them anymore...


1

Nameservers are enough and better. In fact, in case your web hosting changes your IP address (because you haven't a static IP and you're on a shared host), thanks to nameserver you wouldn't need to change record A.



Only top voted, non community-wiki answers of a minimum length are eligible