SERVFAIL/FORMERR/EINVAL on AAAA query
Evaldas Auryla
evaldas.auryla at pheur.org
Thu Jul 27 12:48:03 UTC 2006
Mark Andrews wrote:
>
> Note the SOA record in the last response should be owned
> by emi.lancasterlabs.com not lancasterlabs.com. Named
> rejects answers which move back up heirachy.
>
> Mark
>
> com. 172800 IN NS L.GTLD-SERVERS.NET.
> com. 172800 IN NS M.GTLD-SERVERS.NET.
> com. 172800 IN NS A.GTLD-SERVERS.NET.
> com. 172800 IN NS B.GTLD-SERVERS.NET.
> com. 172800 IN NS C.GTLD-SERVERS.NET.
> com. 172800 IN NS D.GTLD-SERVERS.NET.
> com. 172800 IN NS E.GTLD-SERVERS.NET.
> com. 172800 IN NS F.GTLD-SERVERS.NET.
> com. 172800 IN NS G.GTLD-SERVERS.NET.
> com. 172800 IN NS H.GTLD-SERVERS.NET.
> com. 172800 IN NS I.GTLD-SERVERS.NET.
> com. 172800 IN NS J.GTLD-SERVERS.NET.
> com. 172800 IN NS K.GTLD-SERVERS.NET.
> ;; Received 511 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 169 ms
>
> lancasterlabs.com. 172800 IN NS ns1.everydns.net.
> lancasterlabs.com. 172800 IN NS ns2.everydns.net.
> lancasterlabs.com. 172800 IN NS ns3.everydns.net.
> lancasterlabs.com. 172800 IN NS ns4.everydns.net.
> ;; Received 187 bytes from 192.48.79.30#53(J.GTLD-SERVERS.NET) in 322 ms
>
> emi.lancasterlabs.com. 3600 IN NS linkproof-1.lancasterlabs.com.
> emi.lancasterlabs.com. 3600 IN NS linkproof-2.lancasterlabs.com.
> ;; Received 123 bytes from 63.219.183.200#53(ns4.everydns.net) in 241 ms
>
> lancasterlabs.com. 86400 IN SOA lancasterlabs.com. administrator
> .lancasterlabs.com. 998545544 28800 7200 604800 86400
> ;; Received 143 bytes from 65.163.209.74#53(linkproof-1.lancasterlabs.com) in 25
> 3 ms
I see, does it look like delegation ? Then maybe it's not a good idea to
delegate records for MX hosts ?
Also SOA serial numbers are different on ns1.everydns.net. and
linkproof-1.lancasterlabs.com., looks like split DNS with both parts
exposed to Internet.
iss.it has the same setup for their MX, and I guess there are others.
The bad thing is that you only notice the problem when sendmail tries to
deliver mail from ipv6 enabled box, the A queries work like a charm
because there is an answer and we see no "killer" SOA replies.
Thanks for the explanation.
Regards,
Evaldas
More information about the bind-users
mailing list