Joined: 07 Aug 2013
Location: Florida - United States
|Posted: Wed Aug 07, 2013 8:17 pm Post subject: BIND 9+ IPV6 Resolution Errors
|I found that starting in v9 BIND attempts to resolve lookups for both IPV4 and IPV6 as default - even if the host system doesn't have IPV6 configured.
You may get errors similar to this in the /var/log/messages log:
named: error (network unreachable) resolving 'serer2/AAAA/IN': 2001:503:ba3e::2:30#53
A workaround is to start the named in IPV4 mode.
You can do this by creating/editing /etc/default/named and adding NAMED_OPTIONS="-4" and then restarting bind /etc/rc.d/rc.bind restart