Description of problem:
I'm largely stealing this from a Fedora 11 bug #522999 cause now RH5.4 is behaving the same way.
BIND is sending forward lookup requests using IPv6 when no publicly routable
IPv6 address is assigned to the server.
Version-Release number of selected component (if applicable):
Sep 17 16:15:07 nsserver named: network unreachable resolving 'ns2.vistaprint.com/A/IN': 2001:503:a83e::2:30#53
Sep 17 16:15:07 nsserver named: network unreachable resolving 'ns201.vistaprint.com/A/IN': 2001:503:a83e::2:30#53
Sep 17 16:15:07 nsserver named: network unreachable resolving 'ns2.vistaprint.com/AAAA/IN': 2001:503:a83e::2:30#53
This has only appeared in 5.4
Is this now the expected behaviour ? As in are we supposed to just put in OPTIONS="-4"" to /etc/sysconfig/named ?
Adding -4 to OPTIONS in /etc/sysconfig/named is a workaround, but when NETWORKING_IPV6=no in /etc/sysconfig/network I guess bind shouldn't try to use IPv6 for lookups.
has this been looked at? still unresolved?
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Are you still able to reproduce this issue, please? It is no longer present on my machine with the latest bind-9.3.6-20.P1.el5.
I still get this if I remove OPTIONS="-4" from /etc/sysconfig/named
I don't (unlike another on here have NETWORKING_IPV6=no) anywhere I just don't have IPv6 explicitly configured.
So it is getting an IPv6 address (default):
[root@dns1 /]# /sbin/ifconfig bond0
bond0 Link encap:Ethernet HWaddr 00:19:B9:F3:76:15
inet addr:10.1.50.10 Bcast:10.1.50.255 Mask:255.255.255.0
inet6 addr: fe80::219:b9ff:fef3:7615/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:109560530 errors:0 dropped:0 overruns:0 frame:0
TX packets:112428679 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:77519021142 (72.1 GiB) TX bytes:92995543557 (86.6 GiB)
Not sure what is required here (or documented best practice). Should we have IPv6 explicitly disabled (on this interface IPV6INIT=no)?
Maybe not a bug or I need to RTFM for best practice?
I'm not sure if it's related to this issue, but there is an interesting RFC:
Default Address Selection for Internet Protocol version 6 (IPv6) http://tools.ietf.org/html/rfc3484
... But if the node has assigned only a link-local IPv6 address and a global IPv4 address, then IPv4 is the best choice for communication. ...
I have the same problem with CentOS release 5.8 (Final) running bind-9.3.6-20.P1.el5_8.1
IPv6 was always disabled in the configuration. After upgrade from 5.3 to 5.8 /sbin/ifconfig reported IPv6 adresses although /etc/sysconfig/networking/profiles/default/ifcfg-eth1 contains (and always contained) IPV6INIT=no
I used recommendation by Daniel Walsh as per https://bugzilla.redhat.com/show_bug.cgi?id=641836#c17 and /sbin/ifconfig now shows only IPv4 adresses yet logwatch sends me every day a few hundred messages as
--------------------- Named Begin ------------------------
network unreachable resolving '18.104.22.168.in-addr.arpa/PTR/IN': 2001:13c7:7002:3000::10#53: 1 Time(s)
network unreachable resolving '22.214.171.124.in-addr.arpa/PTR/IN': 2001:67c:e0::3#53: 1 Time(s)
network unreachable resolving '126.96.36.199.in-addr.arpa/PTR/IN': 2001:67c:e0::5#53: 1 Time(s)
IPv6 is still experimental on our LAN and all outgoing IPv6 traffic is intentionally blocked by the firewall.
Since RHEL 5 is now in production phase 2 (only important/critical bugs are fixed), I'm closing this issue because it's not critical.
Please either specify OPTIONS='-4' in /etc/sysconfig/named to tell named not to use IPv6 or disable IPv6 completely on your machine. You can disable IPv6 this way:
"options ipv6 disable=1" to /etc/modprobe.conf
"NETWORKING_IPV6=no" to /etc/sysconfig/network