Old/New DNS Info Munged.. :-(

[Chip Old]

This same problem was covered here a couple of weeks ago, but in your case
we can't check it out because you supplied anonymized data.  Don't do that
if you want better than guesswork as an answer.

Was "www.mydomain.com" formerly a nameserver for "mydomain.com"?  Use dig
to look up "www.mydomain.com" on the GTLD name servers
(a.gtld-servers.net, etc).  You'll probably get an "A" record back
pointing at the old IP address.  Then do a host lookup in the NSI whois
database.  You'll probably find "www.mydomain.com" there with its old IP
address.  You need to modify the host record or delete it, which ever is
appropriate.

On Sat, 14 Apr 2001, Scott Burkett wrote:

> I'm pulling my hair out on this on.  I'm a fairly experienced DNS guy,
> but this is strange.
>
> Scenario:
>
> mydomain.com was being hosted on a co-located box at ISP #1.  IP address
> for this box was 111.111.111.111.  This ran for several years with no
> problems - then, I switched ISPs, moving the box to a new data center.
> The new IP is 222.222.222.222.  The routine name server changes were
> made at networksolutions.com.
>
> The problem:
>
> Total chaos.  After two weeks of "waiting" and "resubmitting", many of
> my customers still cannot access the site.  After investigation, dig
> reports the following:
>
> ; <<>> DiG 8.3 <<>> @ns.somewhere.com www.mydomain.com
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
> ;; QUERY SECTION:
> ;;      www.mydomain.com, type = A, class = IN
>
> ;; ANSWER SECTION:
> www.mydomain.com.      1d23h51m56s IN A  111.111.111.111
>
> ;; AUTHORITY SECTION:
> mydomain.com.          1d23h51m56s IN NS  NS2.NEWISP.com.
> mydomain.com.          1d23h51m56s IN NS  NS.NEWISP.com.
>
> ;; ADDITIONAL SECTION:
> NS2.NEWISP.com.  1d12h57m37s IN A  333.333.333.333
> NS.NEWISP.com.  1d12h57m37s IN A  444.444.444.444
>
> ;; Total query time: 50 msec
> ;; FROM: www.mydomain.com to SERVER: ns.somewhere.com
> ;; WHEN: Sat Apr 14 20:22:17 2001
> ;; MSG SIZE  sent: 35  rcvd: 134
>
> As you can see from the above dump, mydomain.com is listed properly with
> the nameservers from the new ISP.  However, there is still an A record
> floating around, for www.mydomain.com, which points to the old address.
>
> Doing a dig on the new ISP's zone file shows no sign of the old IP at
> all.
>
> Any thoughts before I take my own life over this? :-)

-- 
Chip Old (Francis E. Old)               E-Mail:  fold at bcpl.net
Manager, BCPL Network Services          Voice:   410-887-6180
Manager, BCPL.NET Internet Services     FAX:     410-887-2091
320 York Road
Towson, Maryland 21204-5179 U.S.A.