Re: FORMERR resolving AAAA/IN records [solved]

2009-03-27 Thread Oliver Henriot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Barry and list users, Thanks for the info. - From what you tell me, there's not much more to do than reduce logging of this type of error on my side, so the logging info you gave in 2006 solves my problem just fine. Thank you very much for your

FORMERR resolving AAAA/IN records

2009-03-26 Thread Oliver Henriot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear list users, I have a bind 9.3 server on a centos 5.2 machine which logs huge (about 12 errors every second) quantities of FORMERR messages while trying to resolve /IN records which look like this : Mar 25 08:44:24 myserver named[1124]:

Re: FORMERR resolving AAAA/IN records

2009-03-26 Thread Jeremy C. Reed
Mar 25 08:44:24 myserver named[1124]: FORMERR resolving 'auniarael.com//IN': 216.69.185.38#53 The negative response includes the optional NS records. My custom named has logging that says: FORMERR: NS name matches domain name. This new logging is not committed yet. If you have a

Re: FORMERR resolving AAAA/IN records

2009-03-26 Thread Mark Andrews
In message 20090326141903.1917917...@britaine.cis.anl.gov, b19...@anl.gov writ es: Oliver Henriot oliver.henr...@imag.fr wrote: dnsserver% !! dig auniarael.com @216.69.185.38 ; DiG 8.3 auniarael.com @216.69.185.38 ; (1 server found) ;; res options: init recurs defnam