Bug 1999857

+++ This bug was initially created as a clone of Bug #1999691 +++

+++ This bug was initially created as a clone of Bug #1999334 +++

Description of problem:
On boot, named will not listen on TCP sockets of all specified (or any) IP addresses. This appears to be an ordering problem during startup. When service is restarted by hand, it starts listening on TCP too.

Version-Release number of selected component (if applicable):
bind-9.16.20-3.fc34.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Configure specific IPs in listen-on/listen-on-v6 directives or any.
2. Boot machine with named-chroot service enabled.
3. Named only listening on all IPs over UDP.

Actual results:
Listens on all addresses over UDP only.

Expected results:
Should listen on TCP too, not just on the loopback address.

Additional info:
I tried adding:
-----
[Unit]
Wants=network-online.target
After=network-online.target
-----

in /etc/systemd/system/named-chroot.service.d/named-chroot.conf file and that did help.

--- Additional comment from Petr Špaček on 2021-08-31 09:21:39 CEST ---

I think this is related to upstream issue #2852, please continue there.

--- Additional comment from Petr Menšík on 2021-08-31 16:15:17 CEST ---

Indeed, Petr seems to be correct, it looks related to upstream issue linked.

Can you please check journalctl would contain additionally listening?

journalctl -xeu named-chroot | grep 'additionally listening'

I were unable to reproduce this issue on my test machine. My named listens on all IPs with both UDP and TCP, checked by:
lsof -n -p $(pidof named) | grep :domain

Is this issue reproducible on every reboot on your system?
Would "rndc scan" command fix missing listeners?

--- Additional comment from Petr Menšík on 2021-08-31 17:06:24 CEST ---

I were able to reproduce this issue with reproducer script provided on upstream. It seems reliable when named starts and passes scanning of addresses in correct place.