FORMERR
Jeremy C. Reed
jreed at isc.org
Fri Dec 4 21:03:54 UTC 2009
The upcoming BIND 9.7.0 has several logging improvements, for example:
04-Dec-2009 14:46:41.020 resolver: notice: DNS format error from
216.137.38.22#53 resolving d2rdfnizen5apl.stl2.cloudfront.net/AAAA for
client 127.0.0.1#53764: invalid response
04-Dec-2009 14:46:41.060 resolver: notice: DNS format error from
216.137.38.23#53 resolving d2rdfnizen5apl.stl2.cloudfront.net/AAAA for
client 127.0.0.1#53764: invalid response
The comments in the source for that one is:
/*
* The responder is insane.
*/
Also the query-errors logging (already in recent BIND releases) says:
04-Dec-2009 14:46:41.060 query-errors: debug 1: client 127.0.0.1#53764:
query failed (SERVFAIL) for d2rdfnizen5apl.stl2.cloudfront.net/IN/AAAA
at query.c:4673
That line number in my code has:
/*
* Something has gone wrong.
*/
04-Dec-2009 14:46:41.060 query-errors: debug 2: fetch completed at
resolver.c:3024 for d2rdfnizen5apl.stl2.cloudfront.net/AAAA in 0.079283:
failure/success
[domain:stl2.cloudfront.net,referral:0,restart:2,qrysent:2,timeout:0,lame:0,
neterr:0,badresp:2,adberr:0,findfail:0,valfail:0]
/*
* Something bad happened.
*/
Sorry, even with the new logging, this one is not answered adequately...
will need to look further.
More information about the bind-users
mailing list