Bind is updating DNS with wrong resolver info after rndc flush expires
- by RussH
I'm running Bind 9 on a small office server (Centos 5) with a local mailserver. There's a domain we need to email - it shows wrong DNS info for the MX servers using the local bind, so an RNDC flush updates this correctly - but then, after some time - it reverts back to the wrong resolver.
I would have thought that 'rndc flush' just clears the local cache and pulls all the authoritative info down - so why is it being overwritten (by what seems like the next update)?
where do I need to look? Presumably there's some named logging(?) to determine where it's getting the [new or cached] updates from?