Thanks, I was able to setup a forward zone in the caching servers for
supernet.com and forward to the ns{2,3}.earthlink.net servers.
I will check periodically for their fixing of the zone and then remove
the forward zone in the caching servers.
Is there a simple tool to quickly identify this kind
It's because the NS RRSet returned by the authoritative name servers lists
servers that are not authoritative. Classic DNS mistake.
The com zone says that the authoritative servers for supernet.com are
ns{2,3}.earthlink.net (delegation).
But supernet.com as hosted on ns{2,3}.earthlink.net says
Forgot to additionally add that the only thing that showed up in the
logs was the query log entry, nothing else pertaining the below query. I
also checked with tcpdump on the caching server that it was not sending
any queries towards the Earthlink IP addresses which makes sense given
that the SERVF
When doing a recursive query for MX supernet.com against a caching BIND
server, the BIND server responds back with the answer. The TTL is 300.
After the TTL expires the following recursive query for the same record
returns a SERVFAIL from the caching server.
If I do a +trace on the same query to
4 matches
Mail list logo
