BIND slave stops updating from master after 1-3 days

[Steven Carr]

On 30 July 2013 22:52, Brandon Whaley <brandonw at inmotionhosting.com> wrote:

> Once every few minutes the reload occurs on the master, which sends the
> notify to our slave servers, who should check serials on all the masters
> and transfer from the latest.
>

I think this is your problem. From what I understand BIND does not do this.
It will contact the last server that it received an update from and check
the serial, if it's greater then it will update, but it certainly won't
chase around each master server looking to see if one of them has a higher
version.

I think you need to fix the way you have implemented the masters, BIND
doesn't support multi-master DNS which is what you are trying to implement.
If you need this functionality then Microsoft does (to a point, there still
is effectively a master but as it's distributed through LDAP it handles
multiple updates in the background using a timestamp of the update as the
decider) but then IMHO it's just not BIND.

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130730/0144f01f/attachment.html>