> | nslookup quickbuild.pearsoncomputing.net > > tokra@MD10 ~ $ nslookup quickbuild.pearsoncomputing.net > Server: 195.216.160.130 > Address: 195.216.160.130#53 > > ** server can't find quickbuild.pearsoncomputing.net: NXDOMAIN > > > > > tokra@MD10 ~ $ dig quickbuild.pearsoncomputing.net > > ;; AUTHORITY SECTION: > pearsoncomputing.net. 10792 IN SOA ns1.pearsoncomputing.net. > kb9vqf.pearsoncomputing.net. 201103150 14400 28800 2419200 86400 > > > > > tokra@MD10 ~ $ dig @ns1.pearsoncomputing.net > quickbuild.pearsoncomputing.net > > ;; ANSWER SECTION: > quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181 > > ;; AUTHORITY SECTION: > quickbuild.pearsoncomputing.net. 86400 IN NS ns1.pearsoncomputing.net. > > > > > tokra@MD10 ~ $ dig @ns1.twisted4life.com quickbuild.pearsoncomputing.net > > ;;; ANSWER SECTION: > quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181 > quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181 > > ;; AUTHORITY SECTION: > quickbuild.pearsoncomputing.net. 86400 IN NS ns1.pearsoncomputing.net. > > ;; ADDITIONAL SECTION: > ns1.pearsoncomputing.net. 86400 IN A 74.84.118.180 > > > OK, thanks for the data. I really have no idea what is going on; the fragmentation suggests invalid data floating around the DNS network upstream from me. I have pushed out new DNS records to hopefully override the invalid/corrupted data; give it 24 hours and see if the problem resolves. Sorry for the inconvenience! Tim