Bind 9.2: Nameserver IP change not being recognized by the world
This is a discussion on Bind 9.2: Nameserver IP change not being recognized by the world within the Bind Users forums, part of the DNS and Related Forums category; We are running Bind 9.2 on our Redhat linux servers. Last week, I added a new DNS server, dns3....
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
11-22-2004
|
|||
|
|||
Bind 9.2: Nameserver IP change not being recognized by the world
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 -- Dov Rosenberg Conviveon Corporation http://www.conviveon.com 
|
Linear Mode
