 |
 |
Carl, I took a look at a couple different "whois" sites (whois.net, and also "who.godaddy.com"), and both return ns07 and ns08, which are the two name servers that have the old data. It would seem from this that the problem is entirely an internal one at GoDaddy. Doug On Wed, Apr 21, 2010 at 12:42:39PM -0400, Carl Raymond wrote: > Thanks for the reply, Alec. This all started last week on Monday -- plenty > of time for changes to propagate, and from what I can see, not one change > has. I was doing similar diggery myself, getting the same results. On the > GoDaddy DNS configuration site, it shows different authoritative name > servers (ns33 and ns34 vs. ns07 and ns08). When I would dig with ns07, I > would get the old IP address; with ns33, which is supposed to be > authoritative, I would get NXDOMAIN. I tried adding a new A record as a > diagnostic. That should sidestep any caching of old info, because there > isn't any old info. But a query on the new name would return NXDOMAIN days > later. What was most frustrating is that the GD people weren't very > concerned about the authoritative name server discrepancy, and in fact > hadn't heard of dig at all. Their answer to everything was that it just > needs time to propagate. > > > Carl -- Doug Nelson, Network Architect | [log in to unmask] Academic Technology Services | Ph: (517) 353-2980 Michigan State University | http://www.msu.edu/~nelson/