Bind 9.2: Nameserver IP change not being recognized by the world

[David Botham]

bind-users-bounce at isc.org wrote on 11/22/2004 04:36:27 PM:
> We are running Bind 9.2 on our Redhat linux servers. Last week, I added 
a
> new DNS server, dns3.conviveon.com into our registrar record with 
Network
> Solutions. I had mistakenly set the IP address in our DNS to the wrong
> address, .33 instead of .36. NetworkSolutions resolved the IP to .33 
when I
> added the new nameserver record in. After the fact I realized that I had
> made the mistake and changed our A record for dns3.conviveon.com to 
point to
> the correct IP - .36. After a week and a registrar change (from NetSol 
to
> eNom) the ip address for dns3 is still not being propgrated properly.
> Any suggestions on how to get the change to go thru so the world will
> resolve it properly? I have had this problem with any other DNS record 
we
> manage (>1000 records). Thanks in advance

Go to your current registrar and update the "host" record for dns3.  The 
Gtld name server have the old glue RR for some reason:

; <<>> DiG 9.3.0 <<>> dns3.conviveon.com @216.199.173.5 +trace
;; global options:  printcmd
.                       281537  IN      NS      a.root-servers.net.
.                       281537  IN      NS      b.root-servers.net.
.                       281537  IN      NS      c.root-servers.net.
.                       281537  IN      NS      d.root-servers.net.
.                       281537  IN      NS      e.root-servers.net.
.                       281537  IN      NS      f.root-servers.net.
.                       281537  IN      NS      g.root-servers.net.
.                       281537  IN      NS      h.root-servers.net.
.                       281537  IN      NS      i.root-servers.net.
.                       281537  IN      NS      j.root-servers.net.
.                       281537  IN      NS      k.root-servers.net.
.                       281537  IN      NS      l.root-servers.net.
.                       281537  IN      NS      m.root-servers.net.
;; Received 244 bytes from 216.199.173.5#53(216.199.173.5) in 40 ms

com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
;; Received 508 bytes from 198.41.0.4#53(a.root-servers.net) in 30 ms

dns3.conviveon.com.     172800  IN      A       209.208.11.33
conviveon.com.          172800  IN      NS      dns1.conviveon.com.
conviveon.com.          172800  IN      NS      dns2.conviveon.com.
conviveon.com.          172800  IN      NS      dns3.conviveon.com.
;; Received 152 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 20 ms


Notice that the last line indicates the previous block of answers was 
obtained from A.GTLD-SERVERS.NET.  You may have to bang on their heads a 
little, but, if you call tech support and explain the problem I am sure 
they will update the glue for you.


hth,


Dave...

> 
> 
> -- 
> Dov Rosenberg
> Conviveon Corporation
> http://www.conviveon.com
> 
> 
> 
>