Bind9 error on IPv6

[Mark Andrews]

> >>Im trying to run a DNS server on a pure ipv6 network using bind9.
> > 
> > 
> > 	Well what version of BIND 9 are you talking about?  This
> > 	is like saying "I am driving a Ford something" where something
> > 	is a model that has been released for multiple years.
> 
> Well sorry for the lack of information.
> 
> Im running my dns server on a Fedora Core 3 box and using BIND version 
> 9.2.5-3.
> 
> > 
> > 	No, you don't find these three lines.
> > 
> > 	If you want help don't mangle the diagnostics.  You have no
> > 	idea about what is / is not significant so don't stuff around
> > 	with them.
> >  
> 
> Ok let me clarify what I ment by sniffing i my log.
> 
> I have two computers. One of them is acting as a dns server with ipv6 
> address "fe80::201:2ff:fe77:9157". Besides running BIND im also 
> monitoring all errors who goes to /var/log/messages using "tail -f 
> /var/log/messages".
> 
> My other computer who is acting as a client and has ipv6 address 
> "fe80::201:2ff:fe77:91d2" are trying to connect to the dns server using 
> "dig @fe80::201:2ff:fe77:9157 some.host.at.my.domain.com"
> 
> However for some reason my client is returning with the error message 
> "connection timed out".
> 
> My server on the other hand appends the following lines to 
> /var/log/messages:
> 
> named[2502]: socket.c:1115: unexpected error:
> named[2502]: internal_send: fe80::201:2ff:fe77:91d2#32829: Invalid argument
> named[2502]: client fe80::201:2ff:fe77:91d2#32829: error sending 
> response: invalid file
> named[2502]: socket.c:1115: unexpected error:
> named[2502]: internal_send: fe80::201:2ff:fe77:91d2#32829: Invalid argument
> named[2502]: client fe80::201:2ff:fe77:91d2#32829: error sending 
> response: invalid file
> 
> I've tried to connect to my server from 3 other machines on same net 
> with similar errors on both client and server, so I'm wondering what is 
> wrong?
> 
> All my clients is also running Fedora Core 3 with ipv6 support.

	Firstly upgrade to BIND 9.3.1.  BIND 9.2.x doesn't support
	scaning the IPv6 interface table, it just listens on the
	wildcard port and requires the kernel to provide the scope
	id in the packet info.  

	You are using link-local addresses and the kernel is complaining
	that it can't determine which interface to send the packet out.

	Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org