Web Hosting Talk







View Full Version : Nameserver Issue - Propogation


snlildude87
03-15-2007, 12:16 AM
So earlier today, I changed the nameservers on my domain name (nerdnirvana.org) from ns1[ns2].dreamhost.com to ns1[ns2].nerdnirvana.org just to make sure that my custom nameservers were working.

They were, and it didn't take long for it to propogate. I changed it back to the dreamhost nameservers because I still needed their service.

That was 5 hours ago, and my site has yet to work...at least on my computer.

I contacted dreamhost, and they said that they were able to see my blog, but for some reason, I'm getting an open directory (which is what it should be if the nameservers were still set to ns1[ns2].nerdnirvana.org. You guys should be able to see my blog if you go to nerdnirvana.org, too.

Does anyone know why only I am having this problem (not seeing my blog)? I tried ipconfig /flushdns, restarting my internet connection, clearing out cache/cookies/history, but nothing seems to work....

tiggee
03-15-2007, 12:52 AM
You have a TTL that is set on your NS records in your ns*.nerdnirvana.org domain. (These name servers do not exist by the way, I just tried to query them and they do not exist).
This TTL is passed to the resolving name server (as glue records) and tell the resolving name server to use those name servers for a set period of time.
You have to wait for this period of time (so it can expire from the resolving name server) so it will then query the ORG name servers again and get your dreamhost name servers.

This is why changing name servers can take a day or two before "everyone" sees the change.

snlildude87
03-15-2007, 01:25 AM
You have a TTL that is set on your NS records in your ns*.nerdnirvana.org domain. (These name servers do not exist by the way, I just tried to query them and they do not exist).
This TTL is passed to the resolving name server (as glue records) and tell the resolving name server to use those name servers for a set period of time.
You have to wait for this period of time (so it can expire from the resolving name server) so it will then query the ORG name servers again and get your dreamhost name servers.

This is why changing name servers can take a day or two before "everyone" sees the change.

So it'll take a day or two at most for everyone, including myself, to see the change?

And I swear the nameservers exist (at least, I'm able to ping their IP addresses). That's how I was able to change the appearance of my front page.