问题原文
原帖链接 · WoJ · CC BY-SA 3.0
I see lines such as
Feb 13 21:45:48 srv named[2355]: address not available resolving 'secure.gravatar.com/A/IN': 2a04:fa87:ffff::c6b5:7405#53
Feb 13 21:42:29 srv named[2355]: address not available resolving 'la1.akamaiedge.net/AAAA/IN': 2001:500:a8::e#53
in /var/log/syslog despite running bind in IPv4 mode only
srv # cat /etc/default/bind9
# run resolvconf?
RESOLVCONF=no
# startup options for the server
OPTIONS="-u bind -4"
Why is it so?
已采纳解答
原帖链接 · Nicolae Namolovan · CC BY-SA 3.0
If the system is using systemd then editing /etc/default/bind9 will have no effect.
Edit /lib/systemd/system/bind9.service file instead and add -4 option to ExecStart variable. I'm using Ubuntu 16 and had to do that.
ExecStart=/usr/sbin/named -f -4 -u bind
Also double check that after restarting the named is running with -4 option.
There is actually a bug filled about this configuration confusion https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1565060
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
