Im going to change bind to just listen on specified ipv6 addresses to see what happens.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, April 01, 2014 4:35 PM To: [email protected] Subject: RE: socket error on ipv6 link local I'm getting the same errors with bind-9.10.0b2. Just a guess but I think it's related to using a HE IPv6 Tunnel and the updated root servers. On Tue, 1 Apr 2014, Paul A wrote: > Date: Tue, 1 Apr 2014 16:25:43 -0400 > From: Paul A <[email protected]> > To: 'Kevin Darcy' <[email protected]>, [email protected] > Subject: RE: socket error on ipv6 link local > > So Kevin what your saying is someone using my dns created a record > with fe80::? I was under the impression that bind what trying to > listen on that subnet. > > > > Thanks Paul > > > > From: [email protected] > [mailto:[email protected]] On Behalf > Of Kevin Darcy > Sent: Tuesday, April 01, 2014 4:02 PM > To: [email protected] > Subject: Re: socket error on ipv6 link local > > > > My guess would be that some miscreant out there created a glue AAAA > record with an RDATA of "fe80::" and your network stack balks at > connecting to such an abomination. > > > - Kevin > > On 4/1/2014 2:31 PM, Paul A wrote: > > 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 > > > > > > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > [email protected] <mailto:[email protected]> > https://lists.isc.org/mailman/listinfo/bind-users > > > > _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
