socket error on ipv6 link local

[Paul A]

Hi, I have been using bind 9.9.4 for awhile suddenly looking at the looks I
see lots of socket.c errors. Looking at this it seems that bind is
complaining about the link local ipv6 address , I enabled ipv6 awhile back
and I just noticed this.

 

Apr  1 13:05:32 ns1 named[18769]: connect(fe80::#53) 22/Invalid argument

Apr  1 13:05:32 ns1 named[18769]: socket.c:5351: unexpected error:

Apr  1 13:05:32 ns1 named[18769]: connect(fe80::#53) 22/Invalid argument

Apr  1 13:05:32 ns1 named[18769]: socket.c:5351: unexpected error:

Apr  1 13:05:32 ns1 named[18769]: connect(fe80::#53) 22/Invalid argument

Apr  1 13:05:32 ns1 named[18769]: socket.c:5351: unexpected error:

Apr  1 13:05:32 ns1 named[18769]: connect(fe80::#53) 22/Invalid argument

 

 

 

Aside from having my global ipv6 addresses here is the link local on that
box.

 

          inet6 addr: fe80::206:5bff:fe8e:XXXX/64 Scope:Link

 

 

Has anyone ran into this issue, I do have listen-on-v6 { any; }; and im
assuming if I was to just add the global ipv6 ips this would go away but I
guess im wondering does bind not listen bind itself to link local ip as well
? what is the recommended way to go about fixing this. 

 

 

BIND 9.9.4 (Extended Support Version) <id:8f9657aa> built with
'--enable-rrl'

 

 

Thanks, Paul

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20140401/55ef479b/attachment.html>