|
BIND9 with nscache.eu.sixxs.net as forwarders
![[de]](/s/countries/de.gif) Shadow Hawkins on Sunday, 28 March 2010 11:58:09
Hi,
I'm running a Debian box as my local router/gateway and run
a bind dns-server for the local net and added the nscache.eu.sixxs.net
resolvers as forwarders so I'd get google's services via IPv6.
Since setting the nscache servers:
2001:b18:0:1000:2e0:81ff:fe61:ae0d;
2001:1418:10:2::2;
2001:14b8:0:3007::6;
2001:16d8:aaaa:3::2;
2001:41e0:ff00::5;
2001:7b8:3:4f:202:b3ff:fe46:bec;
as forwarders, I get frequend entries in my log regarding lame-servers and FORMERR errors, like:
Mar 27 20:08:47 server named[3113]: lame-servers: info: FORMERR resolving 'chemie.fb2.fh-frankfurt.de/AAAA/IN': 2001:7b8:3:4f:202:b3ff:fe46:bec#53
Mar 27 20:08:47 server named[3113]: lame-servers: info: FORMERR resolving 'chemie.fb2.fh-frankfurt.de/AAAA/IN': 2001:16d8:aaaa:3::2#53
Mar 27 20:08:47 server named[3113]: lame-servers: info: FORMERR resolving 'chemie.fb2.fh-frankfurt.de/AAAA/IN': 2001:14b8:0:3007::6#53
Mar 27 20:08:48 server named[3113]: lame-servers: info: FORMERR resolving 'chemie.fb2.fh-frankfurt.de/AAAA/IN': 2001:b18:0:1000:2e0:81ff:fe61:ae0d#53
Mar 27 20:08:48 server named[3113]: lame-servers: info: FORMERR resolving 'chemie.fb2.fh-frankfurt.de/AAAA/IN': 2001:1418:10:2::2#53
Mar 27 20:08:49 server named[3113]: lame-servers: info: FORMERR resolving 'www.chemie.uni-marburg.de/AAAA/IN': 2001:14b8:0:3007::6#53
Mar 27 20:08:49 server named[3113]: lame-servers: info: FORMERR resolving 'www.chemie.uni-marburg.de/AAAA/IN': 2001:16d8:aaaa:3::2#53
Mar 27 20:08:49 server named[3113]: lame-servers: info: FORMERR resolving 'www.chemie.uni-marburg.de/AAAA/IN': 2001:b18:0:1000:2e0:81ff:fe61:ae0d#53
Mar 27 20:08:49 server named[3113]: lame-servers: info: FORMERR resolving 'www.cci.ethz.ch/AAAA/IN': 2001:16d8:aaaa:3::2#53
Mar 27 20:08:49 server named[3113]: lame-servers: info: FORMERR resolving 'www.chemie.uni-marburg.de/AAAA/IN': 2001:1418:10:2::2#53
Mar 27 20:08:49 server named[3113]: lame-servers: info: FORMERR resolving 'www.chemie.uni-marburg.de/AAAA/IN': 2001:7b8:3:4f:202:b3ff:fe46:bec#53
Mar 27 20:08:50 server named[3113]: lame-servers: info: FORMERR resolving 'www.cci.ethz.ch/AAAA/IN': 2001:b18:0:1000:2e0:81ff:fe61:ae0d#53
Mar 27 20:08:50 server named[3113]: lame-servers: info: FORMERR resolving 'www.cci.ethz.ch/AAAA/IN': 2001:14b8:0:3007::6#53
Mar 27 20:08:50 server named[3113]: lame-servers: info: FORMERR resolving 'www.cci.ethz.ch/AAAA/IN': 2001:1418:10:2::2#53
Mar 27 20:08:50 server named[3113]: lame-servers: info: FORMERR resolving 'www.cci.ethz.ch/AAAA/IN': 2001:7b8:3:4f:202:b3ff:fe46:bec#53
Mar 27 20:08:50 server named[3113]: lame-servers: info: FORMERR resolving 'www.cci.ethz.ch/AAAA/IN': 2001:41e0:ff00::5#53
I googled around a bit and found some tries at an explanation, but all those 'disable ipv6 and the errors will go away'-messages don't help.
Is someone here that can explain what those messages really mean and if I can ignore them or if I have an faulty configuration?
Thanks in advance,
N. Samii
BIND9 with nscache.eu.sixxs.net as forwarders
Carmen Sandiego on Sunday, 25 July 2010 10:47:21
This isn't bad. Just put the following rule into your named.conf where your logging rules are available:
category lame-servers { null; };
Here is a small modified example:
logging {
channel gib_mir_alles { file "/var/lib/named/dev/gib_mir_alles.log" versions 3 size 10m; };
category default { gib_mir_alles; };
category dnssec { null; };
category lame-servers { null; };
category config {null;};
category notify {null;};
category queries {null;};
category security {null;};
category update {null;};
category xfer-in {null;};
category xfer-out {null;};
category general {null;};
category client {null;};
category database {null;};
category network {null;};
category resolver {null;};
};
Cheers
BIND9 with nscache.eu.sixxs.net as forwarders
Shadow Hawkins on Thursday, 23 December 2010 15:09:42
Just saw your message, thanks! Worked like a charm,
|
Posting is only allowed when you are