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.
Description of problem:
On RHEL 7 there seems to be a problem if you define more then one listening ip in /etc/named.conf. If you restart service named, everything looks fine. Listening on all available and configured ip addresses. But if you reboot your server it could be, that named is started, before all configured ip addresses / interfaces are ready to use and because of this named is only listening on some ips or in worst case only on localhost 127.0.0.1.
Temporary workaround which worked for me:
cp /usr/lib/systemd/system/named.service /etc/systemd/system/.
Add Wants=network.target to /etc/systemd/system/named.service
systemctl daemon-reload
Version-Release number of selected component (if applicable): bind-9.9.4-29.el7.x86_64
How reproducible: always, if you have a server with at least 2 interfaces. eth0 looks to the internet and eth1 is the one should listening on port 53.
Steps to Reproduce:
1. yum install bind-* -y
2. vi /etc/named.conf, edit line listen-on port 53 { 127.0.0.1; }; to
listen-on port 53 { 192.168.14.5; 127.0.0.1; }; (or use another ip)
3. systemclt enable named; systemctl start named
4. netstat -anp | grep 53 (everything should be fine)
5. systemctl reboot
6. netstat -anp | grep 53 (only listeing on 127.0.0.1)
Actual results:
Only listening on 127.0.0.1 after reoobt
Expected results:
Should listen also on 192.168.14.5
Additional info:
Description of problem: On RHEL 7 there seems to be a problem if you define more then one listening ip in /etc/named.conf. If you restart service named, everything looks fine. Listening on all available and configured ip addresses. But if you reboot your server it could be, that named is started, before all configured ip addresses / interfaces are ready to use and because of this named is only listening on some ips or in worst case only on localhost 127.0.0.1. Temporary workaround which worked for me: cp /usr/lib/systemd/system/named.service /etc/systemd/system/. Add Wants=network.target to /etc/systemd/system/named.service systemctl daemon-reload Version-Release number of selected component (if applicable): bind-9.9.4-29.el7.x86_64 How reproducible: always, if you have a server with at least 2 interfaces. eth0 looks to the internet and eth1 is the one should listening on port 53. Steps to Reproduce: 1. yum install bind-* -y 2. vi /etc/named.conf, edit line listen-on port 53 { 127.0.0.1; }; to listen-on port 53 { 192.168.14.5; 127.0.0.1; }; (or use another ip) 3. systemclt enable named; systemctl start named 4. netstat -anp | grep 53 (everything should be fine) 5. systemctl reboot 6. netstat -anp | grep 53 (only listeing on 127.0.0.1) Actual results: Only listening on 127.0.0.1 after reoobt Expected results: Should listen also on 192.168.14.5 Additional info: