| 2020-10-15 08:17:14 |
Aristarkh Zagorodnikov |
description |
The details of this issue are available at Debian Bug report #900788 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900788).
The named service in Focal is defined as follows:
$ cat /lib/systemd/system/named.service
[Unit]
Description=BIND Domain Name Server
Documentation=man:named(8)
After=network.target
Wants=nss-lookup.target
Before=nss-lookup.target
[Service]
EnvironmentFile=-/etc/default/named
ExecStart=/usr/sbin/named -f $OPTIONS
ExecReload=/usr/sbin/rndc reload
ExecStop=/usr/sbin/rndc stop
[Install]
WantedBy=multi-user.target
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 crashing of services that resolve domain names on startup, for example, nginx that resolves its proxy upstream servers. |
The details of this issue are available at Debian Bug report #900788 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900788).
The named service in Focal is defined as follows:
$ cat /lib/systemd/system/named.service
[Unit]
Description=BIND Domain Name Server
Documentation=man:named(8)
After=network.target
Wants=nss-lookup.target
Before=nss-lookup.target
[Service]
EnvironmentFile=-/etc/default/named
ExecStart=/usr/sbin/named -f $OPTIONS
ExecReload=/usr/sbin/rndc reload
ExecStop=/usr/sbin/rndc stop
[Install]
WantedBy=multi-user.target
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. |
|
