The answers given by the DNS have a TTL, and will automatically be
flushed when they are no longer valid. Arbitrarily flushing the cache
for everyone is not correct behavior.
What I would suggest doing instead (in your case) is changing the
reconfig to a restart in /etc/network/if-up.d/bind9, which will flush
the cache instead of just noticing IP address changes - it's being on
the different network that is causing you to live in another view (I
hope).
lamont
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
Status: New => Invalid
** Changed in: bind9 (Debian)
Status: New => Invalid
--
bind9 should flush the DNS cache on suspend / resume to avoid stale records
https://bugs.launchpad.net/bugs/306706
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
