Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ 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.
Comment 3RHEL Program Management
2023-03-03 07:27:52 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.