Originally Posted by sg552
see-why.net A 188.8.131.52 14400s[/code]
So as you can see the webhost got failover nameserver (2 different IP) and the client website is hosted elsewhere not on the same server as nameserver. I try to dig the 2 nameserver but no data is found to point/direct me to 184.108.40.206
See that "A" record?
The name servers maintain "pointers" that tell a web browser or email program where to go to find the site. But not every name server has that "A" record; only your "ns1" and "ns2" name servers do.
You enter the domain name "see-why.net" in your browser. Your browser starts asking where the heck it is located, because it really needs the IP address, not the name of the site.
It starts with your local computer's HOSTS file, and then, if not found there, asks the next nearest name server on the Internet. That is usually your ISPs name server. If that name server doesn't know, it queries up the line, finally ending up at one of seven master name server computers. Somewhere along the line, one of the name servers will say "I don't know where that site is, but the authoritative name server
for that site is at 'ns1.example.com' at IP xxx.xx.xx.xxx".
So the browser goes to that name server's IP address, and asks where the site is. That name server says "I have an A record right here that has the exact IP address! Go here!"
That "ns1" and "ns2" name server are the "authoritative name servers" for your site. Why not have your "A" record stored in each and every name server, so you don't have to go bouncing all over the Internet? Because of all that information you see in the name server record ... A records, CNAME records, MX records ... all of that information would have to be stored on each and every name server. That's thousands of times, all over the world.
Instead, each of the name servers simply points to the "authoritative name servers" where all the information is found. Because data transfers at nearly the speed of light, a distributed system like this makes sense.