Arch Linux

rossboulet

Member

Registered: 2017-12-13

Posts: 49

named won't respond on IPv6 after boot

I'm running a DNS server (named from bind) with all packages up to date. When I boot the server, named will answer just fine on IPv4, but refuses connections on IPv6. If I'm on the server, I can connect to ::1, but not from another host on the network via IPv6. As soon as I restart named, it all works fine. I'm wondering if there is a timing issue between the network starting and named. I'm using netctl to manage the network, which assigns static IPv4 and IPv6 addresses.

Any suggestions?

rossboulet

Member

Registered: 2017-12-13

Posts: 49

Re: named won't respond on IPv6 after boot

Update: I created a named.timer in systemd with an OnBootSec=30 to delay the start of named at boot. Seems to work, but is this solved or just a workaround?

/etc/systemd/system/named.timer

[Unit]
Description=Bind DNS Server

[Timer]
OnBootSec=30

[Install]
WantedBy=timers.target

then

# systemctl disable named.service
# systemctl enable named.timer

rossboulet

Member

Registered: 2017-12-13

Posts: 49

Re: named won't respond on IPv6 after boot

FWIW, I can reproduce the issue on a 64-bit machine.

levi

Moderator

From: Yorkshire, UK

Registered: 2018-06-16

Posts: 1,197

Re: named won't respond on IPv6 after boot

Nice, I'd class that as a workaround because I'd expect it to slow down your boot, but the kind you can keep so long as your willing to pay that cost.  I can't find a recent bug on the arch64 bug tracker for this fwiw, so it seems to be a newly identified bug if real, and not a simple misconfiguration or something along those lines.

Unfortunately I have no experience with bind, so I can't really add much if it's a case of the latter

---

Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

deep42thought

Administrator

From: Jena, Germany

Registered: 2017-06-17

Posts: 617

Re: named won't respond on IPv6 after boot

I think, you may need to add a certain "After=" condition. Though, for me, the default one "After=network.target" works perfectly. Does your dns server get its ipv6 address via dhcp or some other externally-assigned means? Maybe, you need to tell named to postpone its startup until whatever service assigns an ipv6 address for you has finished starting up.

regards,
deep42thought