Expirey weirdness - please help!

[Kevin Darcy]

The domain registry has a "host" record for www.1bigred.com with the old
address. This implies that www.1bigred.com was a delegated nameserver at some
time in the past; maybe it still is a delegated nameserver for some domain or
another. The contact for that host record is Sam Saunders. Why don't you ask
him to update or delete the host record?


- Kevin

"darren at 1bigred.com" wrote:

> Hello everybody.  I am having a really strange problem that I can't explain
> at all.  I'm hoping that I'm just being an idiot and there is something I
> can do to fix this.  We recently took over a domain (1bigred.com).  It was
> hosted on an active directory windows 2000 box (blech) and had a serial
> number of something like 1063.  I created new zone files on my bind servers
> and pasted in the record info.  Everything works fine.  (my serial numbers
> follow a date based numbering - 2002021101)
> Three weeks ago I changed the A record for the host www.  90 percent of the
> internet figured this out within a normal period of time.  But even to this
> day, there are a good number of servers out there that are still answering
> the old ip address.
> The TTL on the old server was set to 1 hour.  My new serial number is
> greater than the old one and when I "dig" the servers who answer
> incorrectly, they do see the correct servers as authoritative.  Here are a
> couple of examples for illustration.  The first one is correct, the second
> one is incorrect.
>
> [darren at tao /]$ dig www.1bigred.com
>
> ; <<>> DiG 9.2.0rc3 <<>> www.1bigred.com
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19083
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
>
> ;; QUESTION SECTION:
> ;www.1bigred.com.               IN      A
>
> ;; ANSWER SECTION:
> www.1bigred.com.        600     IN      A       65.115.27.19
>
> ;; AUTHORITY SECTION:
> 1bigred.com.            600     IN      NS      ns1.supplyguys.net.
> 1bigred.com.            600     IN      NS      ns2.supplyguys.net.
>
> ;; ADDITIONAL SECTION:
> ns1.supplyguys.net.     600     IN      A       65.115.27.5
> ns2.supplyguys.net.     600     IN      A       65.115.27.8
>
> ;; Query time: 4 msec
> ;; SERVER: 65.115.27.5#53(65.115.27.5)
> ;; WHEN: Thu Feb 14 17:05:57 2002
> ;; MSG SIZE  rcvd: 131
>
> [darren at tao /]$ dig @ns1.javanet.com www.1bigred.com
>
> ; <<>> DiG 9.2.0rc3 <<>> @ns1.javanet.com www.1bigred.com
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32248
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
>
> ;; QUESTION SECTION:
> ;www.1bigred.com.               IN      A
>
> ;; ANSWER SECTION:
> www.1bigred.com.        91024   IN      A       206.239.81.9
>
> ;; AUTHORITY SECTION:
> 1bigred.com.            91024   IN      NS      NS1.SUPPLYGUYS.NET.
> 1bigred.com.            91024   IN      NS      NS2.SUPPLYGUYS.NET.
>
> ;; ADDITIONAL SECTION:
> NS1.SUPPLYGUYS.NET.     91617   IN      A       65.115.27.5
> NS2.SUPPLYGUYS.NET.     91617   IN      A       65.115.27.8
>
> ;; Query time: 35 msec
> ;; SERVER: 209.94.128.3#53(ns1.javanet.com)
> ;; WHEN: Thu Feb 14 17:07:59 2002
> ;; MSG SIZE  rcvd: 131
>
> What is wrong here?!  This problem isn't simply a bunk DNS server out there.
> There are a good number of systems that haven't yet figured this out.  And
> it's been 3 weeks, so I feel like there must actually be something wrong
> somewhere, but I don't possess the understanding to further diagnose it.
> Please let me know if anyone has any thoughts.
>
> ~ Darren Godfrey
> darren at supplyguys.com