dns update issue

James Chase chase1124 at gmail.com
Wed Jul 24 14:52:51 UTC 2013

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 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130724/96767080/attachment.html>

More information about the bind-users mailing list