<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 06/28/2012 08:07 AM, Gerald Waugh wrote:
<blockquote cite="mid:4FEC5708.60608@frontstreetnetworks.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
Named is filling the log files with errors from ipv6 request<br>
<br>
<br>
named[25860]: network unreachable resolving
'sns.dialtelecom.cz/A/IN': 2001:628:453:420::48#53<br>
named[25860]: network unreachable resolving
'names.dialtelecom.cz/A/IN': 2001:628:453:420::48#53<br>
<br>
</blockquote>
Bumping this thread as we have not received any responses<br>
<br>
=== a couple of the hundreds of thousands of lines in
/var/log/messages ===<br>
network unreachable resolving 'ns1.sea1.afilias-nst.info/A/IN':
2001:500:19::1#53: 2 Time(s)
<br>
network unreachable resolving 'ns1.seasilver.com/A/IN':
2607:f208:206::5#53: 1 Time(s)
<br>
=== 168,205 in the last couple days<br>
<br>
World IPV6 day was Jun 6<br>
This problems started with the yum update below on Jun 18<br>
<pre wrap="">/var/log/yum.log:Jun 18 06:56:33 Updated:
30:bind-chroot-9.3.6-20.P1.el5_8.1.i386
</pre>
None of the 5107R or 5108R name servers exhibit this problem<br>
It is possible the logging may ignore it.<br>
<pre wrap="">latest bind on 5107R and 5108R
bind-9.7.3-8
on 5106R - ns1.inscomp.net
bind-9.3.6-20 - installed June 18</pre>
<br>
we added<br>
OPTIONS="-4" to /etc/sysconfig/named<br>
and to /etc/named.conf - forwards are ISPs named servers<br>
forwarders { 12.127.17.71; 12.127.16.68; };<br>
// turn off IPv6<br>
listen-on-v6 {none;};<br>
<br>
none of the above helps<br>
This problem appears to exist on all 5106R name servers. <br>
<br>
--<br>
Gerald<br>
</body>
</html>