This bug affects among others anyone with intermittent or permanent ipv6 routing problems. Most documented workarounds for ipv6-problems in dual-stack configurations hint at disabling ipv6 in /etc/default/bind9, but that won't work when the file is ignored when systemd is in control of the processes. My suggestion is thus to edit the service-file for bind9 to include the defaults-file, and thus maintain backward compatibility with most of the published documentation. The following service-section in /lib/systemd/system/bind9.service seems to do the job:
This bug affects among others anyone with intermittent or permanent ipv6 routing problems. Most documented workarounds for ipv6-problems in dual-stack configurations hint at disabling ipv6 in /etc/default/bind9, but that won't work when the file is ignored when systemd is in control of the processes. My suggestion is thus to edit the service-file for bind9 to include the defaults-file, and thus maintain backward compatibility with most of the published documentation. The following service-section in /lib/systemd/ system/ bind9.service seems to do the job:
[Service] =-/etc/ default/ bind9 /usr/sbin/ named -f $OPTIONS /usr/sbin/ rndc reload /usr/sbin/ rndc stop
EnvironmentFile
ExecStart=
ExecReload=
ExecStop=