Should this be a bug report or is this misconfiguration.
At this moment I do not have access to RHEL 7.2 system(s) so are unable to verify if this is true for RHEL systems as well.
Named seems to start before network interfaces are up/started and so named does not listen on any configured, in this case, IPv4 addresses.
From /var/log/messages:
Jan 5 02:00:29 server1 named[633]: all zones loaded Jan 5 02:00:29 server1 named[633]: running Jan 5 02:00:29 server1 systemd: Started Berkeley Internet Name Domain (DNS). Jan 5 02:00:29 server1 systemd: Reached target Host and Network Name Lookups. Jan 5 02:00:29 server1 systemd: Starting Host and Network Name Lookups. Jan 5 02:00:29 server1 network: Bringing up loopback interface: [ OK ] Jan 5 02:00:31 server1 network: Bringing up interface eth0: [ OK ]
netstat -tulpen | grep named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 25 13661 633/named tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 25 13667 633/named tcp6 0 0 ::1:53 :::* LISTEN 25 13663 633/named tcp6 0 0 ::1:953 :::* LISTEN 25 13668 633/named udp 0 0 127.0.0.1:53 0.0.0.0:* 25 13660 633/named udp6 0 0 ::1:53 :::* 25 13662 633/named
sudo systemctl restart named.service
sudo netstat -tulpen | grep named
tcp 0 0 192.168.150.2:53 0.0.0.0:* LISTEN 25 15368 955/named tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 25 15366 955/named tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 25 15373 955/named tcp6 0 0 ::1:53 :::* LISTEN 25 15370 955/named tcp6 0 0 ::1:953 :::* LISTEN 25 15374 955/named udp 0 0 192.168.150.2:53 0.0.0.0:* 25 15367 955/named udp 0 0 127.0.0.1:53 0.0.0.0:* 25 15365 955/named udp6 0 0 ::1:53 :::* 25 15369 955/named