• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Ipv6 ip addresses and Named problem

inado1

Basic Pleskian
I have a server with IPV4 and for some reasons when i go to /var/log/messages i get lots of errors from named (bind) that try resolving Ipv6 ips.



Feb 16 05:12:39 hb2074 named[1893]: error (network unreachable) resolving 'ns1.on.net/A/IN': 2001:44b8:8020:ff00::80#53
Feb 16 05:12:39 hb2074 named[1893]: error (network unreachable) resolving 'ns4.on.net/A/IN': 2001:44b8:8020:ff00::80#53
Feb 16 05:12:39 hb2074 named[1893]: error (network unreachable) resolving 'ns1.on.net/AAAA/IN': 2001:44b8:8020:ff00::80#53
Feb 16 05:12:39 hb2074 named[1893]: error (network unreachable) resolving 'ns2.on.net.au/AAAA/IN': 2001:dc0:4001:1:0:1836:0:141#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns2.he.net/AAAA/IN': 2001:470:300::2#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns2.he.net/A/IN': 2001:470:300::2#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns1.he.net/AAAA/IN': 2001:470:300::2#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns1.he.net/A/IN': 2001:470:300::2#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns2.he.net/AAAA/IN': 2001:470:500::2#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns2.he.net/A/IN': 2001:470:500::2#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns1.he.net/AAAA/IN': 2001:470:500::2#53
Feb 16 05:33:20 hb2074 named[1893]: error (network unreachable) resolving 'ns1.he.net/A/IN': 2001:470:500::2#53
Feb 16 05:46:16 hb2074 named[1893]: error (network unreachable) resolving 'sns-pb.isc.org/A/IN': 2001:500:e::1#53
Feb 16 05:46:16 hb2074 named[1893]: error (network unreachable) resolving 'sns-pb.isc.org/AAAA/IN': 2001:500:e::1#53
Feb 16 05:46:16 hb2074 named[1893]: error (network unreachable) resolving 'sns-pb.isc.org/A/IN': 2001:500:71::30#53
Feb 16 05:46:16 hb2074 named[1893]: error (network unreachable) resolving 'sns-pb.isc.org/AAAA/IN': 2001:500:71::30#53
Feb 16 05:46:16 hb2074 named[1893]: error (network unreachable) resolving 'sns-pb.isc.org/A/IN': 2001:500:60::30#53
Feb 16 05:46:16 hb2074 named[1893]: error (network unreachable) resolving 'sns-pb.isc.org/AAAA/IN': 2001:500:60::30#53


In order to fix that, i went to /etc/sysconfig/named and i added a -4 to the list of parameter
OPTIONS="-c /etc/named.conf -u named -n 2 -4" to force Bind to only listen on IPV4 addresses.

Nevertheless, at the next upgrade i wonder if it will be overwritten.

Thank you.
 
Back
Top