Root Nameserver Showing Wrong Address

[Brad Knowles]

At 8:05 AM -0700 5/18/01, Eric Crutchlow wrote:

>  I've had a problem with mail going to the server olie.appweb.com.  Several
>  people, not all, get mail returned as undeliverable.  When I checked out
>  AOL's dns and did a dig, I got the following results.
>
>  olie.appweb.com is showing as 204.247.188.1, when it should show as
>  216.218.222.66.  The twist is that the name servers (ns1, ns2) have the
>  correct ip address and if queried.

	Update your delegations with NSI:

$ whois olie.appweb.com

Whois Server Version 1.3

Domain names in the .com, .net, and .org domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

    Server Name: OLIE.APPWEB.COM
    IP Address: 204.247.188.1
    Registrar: NETWORK SOLUTIONS, INC.
    Whois Server: whois.networksolutions.com
    Referral URL: www.networksolutions.com


>>>  Last update of whois database: Fri, 18 May 2001 01:35:37 EDT <<<

The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
Registrars.


	If you don't need this whois host record anymore, then you should 
have it deleted.

>  The only thought I had was I used a serial number in the format
>  9912010000. When I moved I changed it to 2000010100.  I changed it
>  last night to 99990051700.

	If you changed it, then you didn't reload the nameservers, 
because the old format is still showing up:

$ dig @ns1.appweb.com. appweb.com. soa

; <<>> DiG 9.1.2 <<>> @ns1.appweb.com. appweb.com. soa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7894
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;appweb.com.                    IN      SOA

;; ANSWER SECTION:
appweb.com.             86400   IN      SOA     ns1.appweb.com. 
admin.appweb.com. 1205803892 10800 3600 604800 86400

;; AUTHORITY SECTION:
appweb.com.             86400   IN      NS      ns1.appweb.com.
appweb.com.             86400   IN      NS      ns2.appweb.com.

;; ADDITIONAL SECTION:
ns1.appweb.com.         86400   IN      A       216.218.222.93
ns2.appweb.com.         86400   IN      A       216.218.222.94

;; Query time: 71 msec
;; SERVER: 216.218.222.93#53(ns1.appweb.com.)
;; WHEN: Fri May 18 11:43:36 2001
;; MSG SIZE  rcvd: 138

$ dig @ns2.appweb.com. appweb.com. soa

; <<>> DiG 9.1.2 <<>> @ns2.appweb.com. appweb.com. soa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28922
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;appweb.com.                    IN      SOA

;; ANSWER SECTION:
appweb.com.             86400   IN      SOA     ns1.appweb.com. 
admin.appweb.com. 1205803892 10800 3600 604800 86400

;; AUTHORITY SECTION:
appweb.com.             86400   IN      NS      ns1.appweb.com.
appweb.com.             86400   IN      NS      ns2.appweb.com.

;; ADDITIONAL SECTION:
ns1.appweb.com.         86400   IN      A       216.218.222.93
ns2.appweb.com.         86400   IN      A       216.218.222.94

;; Query time: 71 msec
;; SERVER: 216.218.222.94#53(ns2.appweb.com.)
;; WHEN: Fri May 18 11:44:00 2001
;; MSG SIZE  rcvd: 138


	Moreover, it looks like you probably need to update the version 
of BIND you're using:

$ dig @ns1.appweb.com. version.bind txt chaos

; <<>> DiG 9.1.2 <<>> @ns1.appweb.com. version.bind txt chaos
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26992
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;version.bind.                  CH      TXT

;; ANSWER SECTION:
VERSION.BIND.           0       CH      TXT     "named 
4.9.5-Rel+-Monday-11-November-96\010\009GregSchueman-LarryKahn-VirajBais"

;; Query time: 70 msec
;; SERVER: 216.218.222.93#53(ns1.appweb.com.)
;; WHEN: Fri May 18 11:45:24 2001
;; MSG SIZE  rcvd: 127

$ dig @ns2.appweb.com. version.bind txt chaos

; <<>> DiG 9.1.2 <<>> @ns2.appweb.com. version.bind txt chaos
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58553
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;version.bind.                  CH      TXT

;; ANSWER SECTION:
VERSION.BIND.           0       CH      TXT     "named 
4.9.5-Rel+-Monday-11-November-96\010\009GregSchueman-LarryKahn-VirajBais"

;; Query time: 70 msec
;; SERVER: 216.218.222.94#53(ns2.appweb.com.)
;; WHEN: Fri May 18 11:45:14 2001
;; MSG SIZE  rcvd: 127

	At the very least, I'd suggest that you upgrade to BIND 8.2.4 
(released within the last couple of days or so), or preferably to 
BIND 9.1.2 (released a while earlier).

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'