28 Nov
2012
28 Nov
'12
2:17 a.m.
AFAIK this is because the "primary nameserver" field in the SOA record doesn't one of the NS records in the delegation from the parent zone. Mark Andrews at ISC: https://lists.isc.org/pipermail/bind-users/2010-April/079804.html In theory this indicates a potential MITM attack, but more likely just ignorance of the people running the nameservers, so I'd just filter it. -Martin On Thu, 29 Nov 2012, Richard Hector wrote:
Sorry if this is off topic.
I'm seeing a bunch of this (and have been for ages) in my bind logs:
Nov 28 23:14:58 jet named[28427]: DNS format error from 120.204.202.200#53 resolving ns-os1.qq.com/AAAA: invalid response