Public bug reported:
On rebooting up ubuntu 20.04, named detects available ipv6 address
assigned via router advertisement but fails to listen on it.
`journalctl -b0` shows something like this.
```
Jan 01 15:27:12 cdns named[200]: IPv6 socket API is incomplete; explicitly
binding to each IPv6 address separately
Jan 01 15:27:12 cdns named[200]: listening on IPv6 interface lo, ::1#53
Jan 01 15:27:12 cdns named[200]: listening on IPv6 interface eth0,
fd42:xxxxxxx#53
Jan 01 15:27:12 cdns named[200]: creating TCP socket: address not available
```
It seems named.service is starting up too early. I have tried adding
`After=network-online.target` for named.service but nothing changed.
I could reproduce this on LXD container ubuntu-daily:20.04 and current version
bind9/focal-updates,now 1:9.16.1-0ubuntu2.4 amd64 [installed]
```
lxc launch ubuntu-daily:20.04 cdns
lxc exec cdns -- apt install -y bind9
lxc restart cdns
lxc exec cdns -- ss -tupln | grep :53
```
The final command should print that named listening on a unique local address
generated by LXD.
```
tcp LISTEN 0 10 [fd42:xxxxxxxx]:53
[::]:*
```
A few users noticed this issue and posted workaround on askubuntu.
https://askubuntu.com/questions/1261187/dns-server-does-not-listen-on-ipv6-after-a-reboot
Their workaround, delaying service startup resolved this issue for me.
```
# systemctl edit named
[Service]
ExecStartPre=-/bin/sleep 10
```
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909822
Title:
named fails to listen dynamic ipv6 address on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909822/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
