[Bug 1553176] [NEW] BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[LaMont Jones]

Public bug reported:

Since 2.6, linux has supported nanosecond granular time in stat(2)
returns.  BIND has a comment in the code that it might use it, but
continues to ignore it.

As of 9.9.3b2, named checks the time of (at least) zone files on disk
(expanding to include include files in 9.10.0a2).  Because the check is
only done to a granularity of seconds, changing the zone file twice in
the same second can cause BIND to decide that it need not reload the
zone, even though it is out of date.

** Affects: bind
     Importance: Undecided
         Status: New

** Affects: maas
     Importance: Undecided
         Status: New

** Affects: bind9 (Ubuntu)
     Importance: Undecided
         Status: New

** Patch added: "patch to fix the issue."
   https://bugs.launchpad.net/bugs/1553176/+attachment/4588314/+files/70_precise_time.diff

** Also affects: bind
   Importance: Undecided
       Status: New

** Also affects: maas
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1553176

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions