Earlier I was seeing ns1.kywimax.com in the list but not now. I think maybe he changed the nameservers at tucows but didn't change the NS records on his own DNS servers, so other DNS servers around the net have the stale information cached. Once they expire that data, they should query the root servers.
Luckily as long as the stale NS records are cached, the other records should also be cached. I used to run into this when customers would switch to a new hosting company without telling the old hosting company, whose nameservers still thought they were authoritative for the domain. Forgetting that if a caching nameserver knows the authoritative nameserver, it will just keep asking it are you authoritative, and if it answers yes, there is no need to ever go back to the root servers. In this case though, I think everything will work out OK. -----Original Message----- From: Af [mailto:[email protected]] On Behalf Of George Skorup Sent: Thursday, October 6, 2016 11:10 PM To: [email protected] Subject: [AFMUG] afmug.com DNS Looks like Paul's network is offline. Did the secondary DNS for afmug.com get set up? Doesn't look like it. I'm still seeing ns, ns0 and ns1.pdmnet.net as the name servers. And all three are obviously down. So the list is going to break once everyone's DNS caches expire.
