Bug 1278015

Summary: Problems in bind if you define more then one listening ip and reboot your server
Product: Red Hat Enterprise Linux 7 Reporter: Ralf Germann <rgermann>
Component: bindAssignee: Tomáš Hozza <thozza>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.1CC: bkruell
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 08:16:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ralf Germann 2015-11-04 14:45:41 UTC
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

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 {; }; to
listen-on port 53 {;; }; (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

Actual results:
Only listening on after reoobt

Expected results:
Should listen also on

Additional info:

Comment 2 Tomáš Hozza 2016-05-10 08:16:43 UTC

*** This bug has been marked as a duplicate of bug 1294506 ***