Set the NOADDITIONAL flag for bind. This removes the 5% ttl reduction

for glue records and forces the glue record to be reloaded from the real NS.

The 5% ttl reduction can cause the glue IN A to timeout before the NS
record in certain situations, such as when the domain owner does not match
up NS records with the NIC.   This behavior by domain owners is becoming
more common as primary zone serving iterates through another glue level
(i.e. exodus hosts the master NS's but the customer then redirects the
NS's to the real DNS servers).  The result is that named would appear to
work properly for about 40 minutes, and then unexpectedly fail for that
zone.  This causes named to behave very inconsistently and a google search
shows that it has obviously frustrated many, many people.  So until the bind
guys make named behave consistently (either fail instantly or accomodate the
case), we need to set this option to accomodate the case.  The result
will be much more consistent behavior and fewer head-scratching failures.

MFC after: 3 days

1 files changed, 2 insertions, 1 deletions

diff --git a/usr.sbin/named/Makefile.inc b/usr.sbin/named/Makefile.inc
index 27b8c40aab66..820951d7d8f3 100644
--- a/usr.sbin/named/Makefile.inc
+++ b/usr.sbin/named/Makefile.inc
@@ -17,7 +17,8 @@ DESTSBIN=	/usr/sbin
 DESTHELP=	/usr/share/misc
 
 CFLAGS+=	-I${BIND_DIR}/port/freebsd/include \
-		-I${.CURDIR}/../../contrib/bind/bin/named
+		-I${.CURDIR}/../../contrib/bind/bin/named \
+		-DNOADDITIONAL
 
 # This is mostly for named and named-xfer
 .if defined(USE_LIBBIND)