PDNS & BIND Listening on multiple IP addresses

[radianation]

I have a DNS Only server that is giving me fits. Both Bind and PowerDNS are listening on two ports. This causes the following concern when testing via intodns:

Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.

From what I gather, the configuration for Bind (and PowerDNS) is allowing my server to listen on both IP addresses I have assigned to it. I tried to configure this in the named.conf with listen-on { xxx.xxx.xxx.xxx; }; to no avail.

tcp        0      0 0.0.0.0:53              0.0.0.0:*              LISTEN      12414/pdns_server
tcp        0      0 xxx.xxx.xxx.xxx:953       0.0.0.0:*            LISTEN      12414/pdns_server
tcp6       0      0 :::53                   :::*                   LISTEN      12414/pdns_server
udp        0      0 0.0.0.0:53              0.0.0.0:*                          12414/pdns_server
udp6       0      0 :::53                   :::*                               12414/pdns_server

I have an older DNS only server on Centos 5 that is deprecated. It had a similar setup that I have checked against and the problem does not occur there, but it does on the newer Centos7.

I've seen other posts suggesting checking my DNS, adding/removing entries, etc. None of that worked. It's possible that this is something simple I'm overlooking, but so far nothing. Any help appreciated.

 

[radianation]

I have continued to research and narrowed it down. This specific nameserver is reporting the wrong IP address for itself. When viewing the appropriate named conf file, it shows the right values, but it's reporting wrong. Is there a "global" file that may have this also listed? It's very strange.

 

[radianation]

I found the issue. For anybody else experiencing this conflict...

While the main domain.com.db was correct, there was another file ns2.maindomain.com.db that contained the wrong value. This is not something that was updated at WHM main server level, but something that must have been updated or created by the ns2 standalone DNS. I had to make sure the value there was also correct.

I finally found this by grepping the conf files for the incorrect IP address. Hope that helps somebody else down the road.

 

[cPanelLauren]

I'm glad to see you were able to identify the cause of the issue and thank you for updating here with the outcome.