Re: Exim panics
On Thu, 03 May 2012 21:53:26 +0100, Tony van der Hoff wrote:
> On 03/05/12 20:55, Camaleón wrote:
>> Does bind9 have any problem with ipv6? I didn't notice, at least in my
>> Lenny servers :-?
>>
> Yes, I think it was discussed on this list. Maybe not bind9, but my
> router can't handle ipv6:
None of my ADSL routers do. But this (the traffic between ipv4 and ipv6
backbones) has to be handled transparently by your carrier.
> May 3 21:29:53 tony-lx named[1985]: error (FORMERR) resolving 'telegraph.nestoria.co.uk/AAAA/IN': 178.250.72.132#53
> May 3 21:29:53 tony-lx named[1985]: DNS format error from 178.250.74.132#53 resolving telegraph.nestoria.co.uk/AAAA for client 192.168.1.105#56959: invalid response
Mmm, there should be no need for that, I mean, bind9 can be configured to
don't use ipv6... this is what I get in lenny when daemon starts:
syslog.1:May 4 07:18:51 stt005 named[2382]: loading configuration from '/etc/bind/named.conf'
syslog.1:May 4 07:18:51 stt005 named[2382]: using default UDP/IPv4 port range: [1024, 65535]
syslog.1:May 4 07:18:51 stt005 named[2382]: using default UDP/IPv6 port range: [1024, 65535]
syslog.1:May 4 07:18:51 stt005 named[2382]: no IPv6 interfaces found
syslog.1:May 4 07:18:51 stt005 named[2382]: listening on IPv4 interface lo, 127.0.0.1#53
syslog.1:May 4 07:18:51 stt005 named[2382]: listening on IPv4 interface eth0, 192.168.0.5#53
And I did nothing to disable ipv6 here (in fact, I can see it's enabled at
"/etc/bind/named.conf.options" → listen-on-v6 { any; };" , but still bind9
does this by its own.
> Commenting out the ipv6 entry in hosts fixed that.
And that's strange because if you are using a local dns resolver, the "hosts"
file shouldn't be queried to resolve external domains :-?
>> Mmm, then there must be something at a lower layer, I mean, maybe is
>> that you have disabled the whole ipv6 support at the kernel.
>>
>> I can see my two interfaces are getting an ipv6 address:
(...)
>> And (from my Lenny):
>>
>> sm01@stt008:~$ lsmod|grep ipv6
>> ipv6 288456 26
>>
> Neither of those provokes a response here.
That can mean you have disabled ipv6, system-wide.
Greetings,
--
Camaleón
Reply to: