** Description changed:
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.
[Impact]
- * If a zone file is changed (generally by automated processes) more
+ * If a zone file is changed (generally by automated processes) more
than once in a second, bind9 happily thinks it has already loaded the
zone. A trivial demonstration of the bug can be seen at
- paste.ubuntu.com/23921121/
+ paste.ubuntu.com/23921121/ -- http://paste.ubuntu.com/23921176/ is the
+ same test with the fixed code. Making this a test case is somewhat
+ problematic in that it needs to make sure that they happen inside of the
+ same second.
- * MAAS is exactly the sort of use case that hits this bug.
+ * MAAS is exactly the sort of use case that hits this bug.
- * The upload changes BIND's utility function to actual use the
+ * The upload changes BIND's utility function to actual use the
st_mtim.tv_nsec instead of '0'.
[Test Case]
- * See the pastebin above. (Change a zone file and reload it, and then
+ * See the pastebin above. (Change a zone file and reload it, and then
do it again less than a second later.)
[Regression Potential]
- * Ignoring the whole "rebuilds sometimes break things", the most likely
+ * Ignoring the whole "rebuilds sometimes break things", the most likely
regression would be one where something was either relying on BIND not
reloading the dozone (unlikely), or otherwise relying on the modify time
on a zone file to some arbitrary value.
[Other Info]
- This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March
+ This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March
2016.
** Also affects: bind9 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Xenial)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
