systemd unit service file does not wait for bind9 to be ready
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Debian) |
Fix Released
|
Unknown
|
|||
bind9 (Ubuntu) |
Fix Released
|
Undecided
|
Athos Ribeiro |
Bug Description
The details of this issue are available at Debian Bug report #900788 (https:/
The named service in Focal is defined as follows:
$ cat /lib/systemd/
[Unit]
Description=BIND Domain Name Server
Documentation=
After=network.
Wants=nss-
Before=
[Service]
EnvironmentFile
ExecStart=
ExecReload=
ExecStop=
[Install]
WantedBy=
Alias=bind9.service
Unfortunately, since bind9 starts up asynchronously, the services that depend on nss-lookup.target may fail DNS resolution due to bind9 not being started up in time. This, in some cases, leads to the crashing of services that resolve domain names on startup, for example, nginx that resolves its proxy upstream servers.
Related branches
- Christian Ehrhardt (community): Approve
- Canonical Server: Pending requested
-
Diff: 1340 lines (+1164/-9)7 files modifieddebian/NEWS (+24/-0)
debian/bind9-dnsutils.install (+0/-2)
debian/bind9.apport (+24/-0)
debian/bind9.named.service (+2/-1)
debian/changelog (+1110/-0)
debian/control (+3/-4)
debian/rules (+1/-2)
description: | updated |
Changed in bind9 (Debian): | |
status: | Unknown → Fix Released |
Changed in bind9 (Ubuntu): | |
assignee: | nobody → Athos Ribeiro (athos-ribeiro) |
Thank you for the report Aristarkh.
It is odd that this was fixed so long ago - 1:9.11.4+dfsg-1 is what the debian bug states.
That was only pushed to Debian buster in:
195 bind9 (1:9.11.4+dfsg-1) unstable; urgency=medium
196
197 [ Bernhard Schmidt ]
198 * Use systemd Type=forking to signal daemon init.
199 Thanks to Elie Roudninski (Closes: #900788)
...
209 -- Ondřej Surý <email address hidden> Sat, 14 Jul 2018 12:27:56 +0000
But I don't see it on any path to Debian/sid - not in the past changelogs nor in the currently used .service files.
I need to ask if this might have had an intentional reason ... or if it really was "lost again" later on.