27 Apr
2011
27 Apr
'11
6:14 p.m.
Domain servers in listed order:
ns1.pearsoncomputing.net
ns1.twisted4life.com
So why is pearsoncomputing.net IN NS ns1.pearsoncomputing.net? It's a
recursion unless ns1.pearsoncomputing.net is not set up somewhere on the
highest level.
Which it is--check the root DNS records if you want to. :)
Also, pearsoncomputing.net and all other domains here function perfectly.
The only problem is with *.quickbuild.pearsoncomputing.net, where *
changes somewhat randomly. I have never had an nslookup against
ns1.pearsoncomputing.net fail, and the configuration was not changed until
just now (to force a cache reload on all DNS servers on the Internet) so I
must logically assume the problem was an upstream glitch of some sort. It
would not be the first time something unusual has happened upstream to the
DNS system of any particular website...
Tim