Hi bind-users,
I've encountered an edge case that was not considered while developing
the method that BIND uses to check if a zone file has been modified. I
will immediately state that this is an extreme edge case, but
nonetheless one that should (and can) be avoided with minimal change to
the sou
On Tue, 30 Jun 2015, Milos Ivanovic wrote:
I've encountered an edge case that was not considered while developing
the method that BIND uses to check if a zone file has been modified. I
will immediately state that this is an extreme edge case, but
nonetheless one that should (and can) be avoided
In article ,
Milos Ivanovic wrote:
> To reproduce:
> 1. Set the hardware clock to some time in the future
> 2. Boot the system, including BIND
> 3. Let NTP fix the time, or fix the time manually
> 4. Edit a zone, finishing by increasing its serial
> 5. run `rndc reload yourzone.example.com'
> 6.
In message , Barry Marg
olin writes:
>
> Furthermore, it's not necessarily true that you want to ignore a zone
> file just because it's older than the one previously used. Suppose you
> restore a zone file from a backup, and it gets the original mtime.
> Wouldn't you want a reload to pick this
4 matches
Mail list logo
