Matt, I think you are right. My guess is that for some reason they dropped the domain out of the root servers for a period of time and the major isps grabed the worldnic servers as being authoratative.
Not much we can do, other than wait... Darrell ---------- Original Message ---------------------------------- From: Matthew Bramble <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Sat, 20 Dec 2003 00:02:14 -0500 >Darrell, > >It looks like your name server records were maybe munged for a period of >time from a root update that is now fixed. Those munged records though >are being cached and they should get a good copy once they expire. This >might explain why all of us seem to be able to resolve your domain, >being that we aren't likely to have it cached being smaller providers, >however the larger providers seem to have bad records for it because >they hit your domain while the data was bad. Just guessing of course. > >If you have some local ISP's which are likely to have chached an earlier >copy of the records, try querying their servers to see what it returns. >I suspect that they will have a bad copy also, at least for a short >period of time. I don't believe there is anything you can do about this >if I am correct. > >Matt > > > >Darrell LaRock wrote: > >>Scott, >> >>On the DNSSTUFF, I used the cached ISP report looking at the NS record. What does >>it mean when an ISP has the name server set to ns92.worldnic.com? Does this mean at >>one time when the domain was looked up it was not resolved from the root servers? >> >>AT&T Worldnet #1 NS=ns1.infi.net. [TTL=1d 9h 38m 50s] NS=ns2.infi.net. >>[TTL=1d 9h 38m 50s] >>AT&T Worldnet #2 NS=ns1.infi.net. [TTL=1d 4h 18m 50s] NS=ns2.infi.net. >>[TTL=1d 4h 18m 50s] >>AT&T Worldnet #1 NS=ns1.infi.net. [TTL=1d 2h 53m 53s] NS=ns2.infi.net. >>[TTL=1d 2h 53m 53s] >>AT&T Worldnet #2 NS=ns91.worldnic.com. [TTL=10h 45m 11s] >>NS=ns92.worldnic.com. [TTL=10h 45m 11s] >> >>Taking wild stabs in the dark :) >>Darrell >> >>---------- Original Message ---------------------------------- >>From: "R. Scott Perry" <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>Date: Fri, 19 Dec 2003 22:56:28 -0500 >> >> >> >>>>However, something is seriously wrong as the major ISP's can't resolve it >>>>(Earthlink, Charter, Some AOL Users, Road Runner). This occured right >>>>after the whois info was updated to the new authoratative servers. >>>> >>>> >>>That's probably the problem. >>> >>>Once the first .com parent server gets the new NS records, it takes up to >>>about 6 hours for all the other .com parent servers to get updated, and >>>another 48 hours before TTL values expire on DNS servers throughout the >>>world. Earthlink, Charter, and some other larger ISPs almost certainly >>>have the old values cached, which will take up to 48 hours to expire after >>>the change. During that time, they will be using the old NS records. >>> >>> -Scott >>> >>> > > >--- >[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] > >--- >This E-mail came from the Declude.JunkMail mailing list. To >unsubscribe, just send an E-mail to [EMAIL PROTECTED], and >type "unsubscribe Declude.JunkMail". The archives can be found >at http://www.mail-archive.com. > --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
