Very curious...
That server (cpns01.secureserver.net) is claiming authority for the root
zone, so it's just plain a bad actor. Into my blackhole list it goes,
along with it's friends...
$ dig @216.69.185.38 +norec any .
; <<>> DiG 9.6.0-P1 <<>> @216.69.185.38 +norec any .
; (1 server found)
;;
-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
In message <20090326141903.1917917...@britaine.cis.anl.gov>, b19...@anl.gov writ
es:
> Oliver Henriot 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 dnsrch
Oliver Henriot wrote:
>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]: FORMERR resolving
>'a
> 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
-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]: FORME
6 matches
Mail list logo
