I'm forwarding a MaraDNS question
Sam Trenholme
strenholme.usenet at gmail.com
Tue Nov 4 16:00:19 EST 2008
Since I don't have time to support MaraDNS anymore, I'm forwarding a
question someone sent me via private email (with their permission):
Hi,
I have been using and pimping MaraDNS for a while now, so a quick thanks
for a good alternative DNS resolver.
Now onto a problem I have stumbled on. If I use MaraDNS as a resolver
for a TXT lookup on '25.78.125.74.sa-trusted.bondedsender.org' I get,
after waiting some time, a SERVFAIL...if I use a BIND 'powered' DNS
server I get a NXDOMAIN.
Digging deeping it turns out that bondedsender.org might be doing
something fruity with its answers and MaraDNS is receiving those
responses but are dropping them as they are considered invalid.
Alternatively MaraDNS might be being a pain :)
--
alex at woodchuck:~$ dig +trace TXT 25.78.125.74.sa-trusted.bondedsender.org
; <<>> DiG 9.3.4-P1.1 <<>> +trace TXT 25.78.125.74.sa-trusted.bondedsender.org
;; global options: printcmd
. 57960 IN NS A.ORSN-SERVERS.NET.
. 57960 IN NS B.ORSN-SERVERS.NET.
. 57960 IN NS C.ORSN-SERVERS.NET.
. 57960 IN NS D.ORSN-SERVERS.NET.
. 57960 IN NS E.ORSN-SERVERS.NET.
. 57960 IN NS F.ORSN-SERVERS.NET.
. 57960 IN NS G.ORSN-SERVERS.NET.
. 57960 IN NS H.ORSN-SERVERS.NET.
. 57960 IN NS I.ORSN-SERVERS.NET.
. 57960 IN NS J.ORSN-SERVERS.NET.
. 57960 IN NS K.ORSN-SERVERS.NET.
. 57960 IN NS L.ORSN-SERVERS.NET.
. 57960 IN NS M.ORSN-SERVERS.NET.
;; Received 488 bytes from 127.0.0.1#53(127.0.0.1) in 7 ms
org. 172800 IN NS D0.ORG.AFILIAS-NST.org.
org. 172800 IN NS TLD1.ULTRADNS.NET.
org. 172800 IN NS TLD2.ULTRADNS.NET.
org. 172800 IN NS A0.ORG.AFILIAS-NST.INFO.
org. 172800 IN NS B0.ORG.AFILIAS-NST.org.
org. 172800 IN NS C0.ORG.AFILIAS-NST.INFO.
;; Received 448 bytes from 2a02:60:ffff:1::2#53(B.ORSN-SERVERS.NET) in 38 ms
bondedsender.org. 86400 IN NS s0.returnpath.net.
bondedsender.org. 86400 IN NS s1.returnpath.net.
;; Received 106 bytes from 2001:500:f::1#53(D0.ORG.AFILIAS-NST.org) in 10 ms
sa-trusted.bondedsender.org. 2700 IN NS ltns2.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS xlns2.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS spns4.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS xlns1.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS spns3.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS spns2.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS xlns3.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS spns1.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS ltns3.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS ltns4.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS xlns12.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS spns5.returnpath.net.
sa-trusted.bondedsender.org. 2700 IN NS xlns11.returnpath.net.
;; Received 510 bytes from 216.24.130.19#53(s0.returnpath.net) in 168 ms
;; Received 58 bytes from 64.92.165.122#53(ltns2.returnpath.net) in 114 ms
alex at woodchuck:~$
--
Any ideas, what trivial thing have I missed. A packet capture shows
MaraDNS getting NXDOMAIN from all the authoritive servers, but then
after she has gone through the lot she hits us with a SERVFAIL :-/
Cheers
Alex
More information about the list
mailing list