Quote:
Originally Posted by ddfrench
Here's something I don't follow. If domain A has the wrong server IP address in its DNS record, a request for any page on domain A will generate a response along the lines of "domain not found". If domain A does not exist on the server, it will not return a page from domain B (Alan's domain which is on the server).
If the only response is an error message, I don't see how the DNS errors would cause Alan's problems with Google.
|
Here's an experiment you can perform that will illustrate the situation at hand.
Of IBM's many IP Addresses, one is 129.42.56.216; enter this IP Address into your browser's address bar, hit Enter or Go, and you will get the default page
IBM United States .
If another Domains Name's Name Server points to 129.42.56.216, anyone going to
www.that-other-domain-name.ext will get that IBM page.
However, IBM does
not have any resource at
http://129.42.56.216/my-webproblog , which you can see by clicking on the preceding link, which will yield a Custom 404 error.
And, so will
www.that-other-domain-name.ext/my-webproblog, as such is actually trying to access 129.42.56.216/my-webproblog .
The Domain Name is, via the Name Server, translated into an IP Address; any parameters following the Domain Name are then appended to that IP Address.
If the hostserver at that IP Address has a resource that matches that requested, it will serve it up. And, as the default page require no parameters, a bare IP Address will yield that default page on that IP Addresses's hostserver.