Tinydns configuration... works, but no reverse dns
Jon Radel
jon at radel.com
Fri Apr 4 21:59:46 UTC 2008
John Almberg wrote:
>
> I am using tinydns on my FreeBSD server. Normal DNS lookups work fine,
> but I can't get reverse DNS to work.
>
> My colocation provider says they have delegated DNS to my name servers.
> If there is a way to independently verify this, I don't know how to do
> it, so I am taking their word for it.
I'm a bind guy myself, so I can't answer to your tinydns configuration,
but as to how to independently verify delegation, I find the following
handy:
freesparky# dig +trace -x 66.111.0.194
; <<>> DiG 9.4.2 <<>> +trace -x 66.111.0.194
;; global options: printcmd
. 112878 IN NS A.ROOT-SERVERS.NET.
. 112878 IN NS B.ROOT-SERVERS.NET.
. 112878 IN NS C.ROOT-SERVERS.NET.
. 112878 IN NS D.ROOT-SERVERS.NET.
. 112878 IN NS E.ROOT-SERVERS.NET.
. 112878 IN NS F.ROOT-SERVERS.NET.
. 112878 IN NS G.ROOT-SERVERS.NET.
. 112878 IN NS H.ROOT-SERVERS.NET.
. 112878 IN NS I.ROOT-SERVERS.NET.
. 112878 IN NS J.ROOT-SERVERS.NET.
. 112878 IN NS K.ROOT-SERVERS.NET.
. 112878 IN NS L.ROOT-SERVERS.NET.
. 112878 IN NS M.ROOT-SERVERS.NET.
;; Received 272 bytes from 216.143.151.3#53(216.143.151.3) in 13 ms
66.in-addr.arpa. 86400 IN NS indigo.ARIN.NET.
66.in-addr.arpa. 86400 IN NS BASIL.ARIN.NET.
66.in-addr.arpa. 86400 IN NS henna.ARIN.NET.
66.in-addr.arpa. 86400 IN NS dill.ARIN.NET.
66.in-addr.arpa. 86400 IN NS figwort.ARIN.NET.
66.in-addr.arpa. 86400 IN NS chia.ARIN.NET.
66.in-addr.arpa. 86400 IN NS epazote.ARIN.NET.
;; Received 194 bytes from 2001:dc3::35#53(M.ROOT-SERVERS.NET) in 107 ms
0.111.66.in-addr.arpa. 86400 IN NS auth1.ns.nyi.net.
0.111.66.in-addr.arpa. 86400 IN NS auth2.ns.nyi.net.
;; Received 93 bytes from 192.42.93.32#53(figwort.ARIN.NET) in 94 ms
194.0.111.66.in-addr.arpa. 86400 IN NS ns1.identry.com.
194.0.111.66.in-addr.arpa. 86400 IN NS ns2.identry.com.
194.0.111.66.in-addr.arpa. 86400 IN NS ns3.identry.com.
;; Received 140 bytes from 64.90.175.14#53(auth1.ns.nyi.net) in 16 ms
dig: couldn't get address for 'ns3.identry.com': not found
which does bring up the issue of why you refer to ns0 and ns1 in your
question and your provider delegates to ns1, ns2, and ns3, the last of
which doesn't appear to have an A record anywhere useful.
A retry, using a different NS record this time:
.....trimmed....
194.0.111.66.in-addr.arpa. 86400 IN NS ns1.identry.com.
194.0.111.66.in-addr.arpa. 86400 IN NS ns2.identry.com.
194.0.111.66.in-addr.arpa. 86400 IN NS ns3.identry.com.
;; Received 140 bytes from 64.90.175.14#53(auth1.ns.nyi.net) in 23 ms
194.0.111.66.in-addr.arpa. 3600 IN PTR on.identry.com.
0.111.66.in-addr.arpa. 259200 IN NS ns0.0.111.66.in-addr.arpa.
0.111.66.in-addr.arpa. 259200 IN NS ns1.0.111.66.in-addr.arpa.
;; Received 107 bytes from 66.111.0.253#53(ns1.identry.com) in 17 ms
The PTR record looks reasonable, but those NS records...well. ;-)
--Jon Radel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3283 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20080404/180cd297/smime.bin
More information about the freebsd-questions
mailing list