On Thu, Apr 26, 2007 at 10:06:32AM +0100, Randy Bush wrote:
roam.psg.com:/usr/home/randy> doc -p -w www.cnn.com. Doc-2.2.3: doc -p -w www.cnn.com. Doc-2.2.3: Starting test of www.cnn.com. parent is cnn.com. Doc-2.2.3: Test date - Thu Apr 26 09:04:52 GMT 2007 DIGERR (NOT_AUTHORIZED): dig @dmtns01.turner.com. for SOA of www.cnn.com. failed DIGERR (NOT_AUTHORIZED): dig @dmtns02.turner.com. for SOA of www.cnn.com. failed
I think your debugging tool is faulty, as a dig ns cnn.com @a.gtld-servers.net gives: cnn.com. 172800 IN NS twdns-01.ns.aol.com. cnn.com. 172800 IN NS twdns-02.ns.aol.com. cnn.com. 172800 IN NS twdns-03.ns.aol.com. cnn.com. 172800 IN NS twdns-04.ns.aol.com. twdns-01.ns.aol.com. 172800 IN A 149.174.213.151 twdns-02.ns.aol.com. 172800 IN A 152.163.239.216 twdns-03.ns.aol.com. 172800 IN A 207.200.73.85 twdns-04.ns.aol.com. 172800 IN A 64.12.147.120 All of the above answer to me and have the same serial for cnn.com. I guess your tool probably asks a faulty caching nameserver for the NS records of cnn.com - there are several misguided implementations that cache for a longer period than the TTL of the record states. Having said that and beeing a hostmaster for a large german broadband ISP i am indeed quite thankful for Microsoft ignoring low TTLs in most Windows XP installations especially as todays drones do no seem to care about asking proper IN MX questions. ;-) Stefan -- My software never has bugs. It just develops random features.