dns update issue
This isn't exactly a bind issue but I recently changed our slave dns server to a new IP address in a remote location for our domain 'mandala-designs.com'. I updated our dns record in bind to point to the new location of our dns server: dns3.mandala-designs.com at 192.241.200.20. I added the PTR for the new IP address. I think it's been about 4 weeks since I made this change. However if I try to ping dns3.mandala-designs.com from different network locations it still returns the IP address of our old server, which I have been forced to leave on for now to avoid resolution issues. I can't figure out the reason for this. Our TTL is only 5 minutes so why should people still be getting the wrong address? If you dig @ dns1.mandala-designs.com, the authoritative NS, then you get the correct ip for dns3. What am I not understanding? -- Beware of all enterprises that require new clothes. -- Henry David Thoreau ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: dns update issue
On Wed, Jul 24, 2013 at 10:52:51AM -0400, James Chase chase1...@gmail.com wrote a message of 64 lines which said: However if I try to ping dns3.mandala-designs.com from different network locations it still returns the IP address of our old server, Probably the usual problem with in-zone name servers: glue not modified at the registry. % whois DNS3.MANDALA-DESIGNS.COM ... Server Name: DNS3.MANDALA-DESIGNS.COM IP Address: 216.195.213.58 And, indeed, the registry still serves the old info: % dig @a.gtld-servers.net A DNS3.MANDALA-DESIGNS.COM ... DNS3.MANDALA-DESIGNS.COM. 172800 IN A 216.195.213.58 ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
