From: Brantley Coile <bwc@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ndb reverse lookup
Date: Tue, 1 Jun 2004 14:15:42 -0400 [thread overview]
Message-ID: <b3d1ec3991af339a661a5ce70a629e42@borf.com> (raw)
In-Reply-To: <1ed1feb624a20a068ff048ececb23475@vitanuova.com>
[-- Attachment #1: Type: text/plain, Size: 6196 bytes --]
What do I add to /lib/ndb/local1 to get reverse lookups to work?
205.185.197.119 is a machine in borf.com domain. Which is also
the address of the dns server, so edsac has the same IP address.
baron% ndb/dnsdebug @edsac 205.185.197.119
1.1: sending to 205.185.197.119/edsac 119.197.185.205.in-addr.arpa ptr
1.1: sending to 205.185.197.119/edsac 119.197.185.205.in-addr.arpa ptr
1: rcvd Server failed from 205.185.197.119 (authoritative can_recurse)
Q: 119.197.185.205.in-addr.arpa ptr
Auth: 197.185.205.in-addr.arpa 23 hr 59 min 55 ns as1.icg.net
197.185.205.in-addr.arpa 23 hr 59 min 55 ns as2.icg.net
Hint: as1.icg.net 1 day 23 hr 59 ip 170.147.45.163
as2.icg.net 1 day 23 hr 59 ip 170.147.45.164
1.1: sending to 198.41.0.10/J.ROOT-SERVERS.NET 119.197.185.205.in-addr.arpa ptr
1: rcvd OK from 198.41.0.10 ( recurse)
Q: 119.197.185.205.in-addr.arpa ptr
Auth: arpa 6 day ns A.ROOT-SERVERS.NET
arpa 6 day ns H.ROOT-SERVERS.NET
arpa 6 day ns C.ROOT-SERVERS.NET
arpa 6 day ns G.ROOT-SERVERS.NET
arpa 6 day ns F.ROOT-SERVERS.NET
arpa 6 day ns B.ROOT-SERVERS.NET
arpa 6 day ns K.ROOT-SERVERS.NET
arpa 6 day ns L.ROOT-SERVERS.NET
arpa 6 day ns M.ROOT-SERVERS.NET
arpa 6 day ns I.ROOT-SERVERS.NET
arpa 6 day ns E.ROOT-SERVERS.NET
arpa 6 day ns D.ROOT-SERVERS.NET
Hint: A.ROOT-SERVERS.NET 41 day 16 hr ip 198.41.0.4
H.ROOT-SERVERS.NET 41 day 16 hr ip 128.63.2.53
C.ROOT-SERVERS.NET 41 day 16 hr ip 192.33.4.12
G.ROOT-SERVERS.NET 41 day 16 hr ip 192.112.36.4
F.ROOT-SERVERS.NET 41 day 16 hr ip 192.5.5.241
B.ROOT-SERVERS.NET 41 day 16 hr ip 192.228.79.201
K.ROOT-SERVERS.NET 41 day 16 hr ip 193.0.14.129
L.ROOT-SERVERS.NET 41 day 16 hr ip 198.32.64.12
M.ROOT-SERVERS.NET 41 day 16 hr ip 202.12.27.33
I.ROOT-SERVERS.NET 41 day 16 hr ip 192.36.148.17
E.ROOT-SERVERS.NET 41 day 16 hr ip 192.203.230.10
D.ROOT-SERVERS.NET 41 day 16 hr ip 128.8.10.90
1.2: sending to 198.41.0.4/A.ROOT-SERVERS.NET 119.197.185.205.in-addr.arpa ptr
1: rcvd OK from 198.41.0.4 ( recurse)
Q: 119.197.185.205.in-addr.arpa ptr
Auth: 205.in-addr.arpa 1 day ns chia.ARIN.NET
205.in-addr.arpa 1 day ns dill.ARIN.NET
205.in-addr.arpa 1 day ns henna.ARIN.NET
205.in-addr.arpa 1 day ns indigo.ARIN.NET
205.in-addr.arpa 1 day ns epazote.ARIN.NET
205.in-addr.arpa 1 day ns figwort.ARIN.NET
205.in-addr.arpa 1 day ns ginseng.ARIN.NET
1.5: sending to 205.185.197.119/edsac chia.arin.net ip
1: rcvd OK from 205.185.197.119 ( can_recurse)
Q: chia.arin.net ip
Ans: chia.arin.net 1 day 23 hr 59 ip 192.5.6.32
Auth: arin.net 1 day 23 hr 59 ns aloe.arin.net
arin.net 1 day 23 hr 59 ns b3.nstld.com
arin.net 1 day 23 hr 59 ns c3.nstld.com
arin.net 1 day 23 hr 59 ns chia.arin.net
arin.net 1 day 23 hr 59 ns d3.nstld.com
arin.net 1 day 23 hr 59 ns dill.arin.net
arin.net 1 day 23 hr 59 ns epazote.arin.net
arin.net 1 day 23 hr 59 ns figwort.arin.net
Hint: aloe.arin.net 1 day 23 hr 59 ip 192.12.94.32
b3.nstld.com 1 day 23 hr 59 ip 192.33.14.32
c3.nstld.com 1 day 23 hr 59 ip 192.26.92.32
chia.arin.net 1 day 23 hr 59 ip 192.5.6.32
d3.nstld.com 1 day 23 hr 59 ip 192.31.80.32
dill.arin.net 1 day 23 hr 59 ip 192.35.51.32
epazote.arin.net 1 day 23 hr 59 ip 192.41.162.32
figwort.arin.net 1 day 23 hr 59 ip 192.42.93.32
1.3: sending to 192.5.6.32/chia.arin.net 119.197.185.205.in-addr.arpa ptr
1: rcvd OK from 192.5.6.32 ( recurse)
Q: 119.197.185.205.in-addr.arpa ptr
Auth: 197.185.205.in-addr.arpa 1 day ns as1.icg.net
197.185.205.in-addr.arpa 1 day ns as2.icg.net
1.6: sending to 205.185.197.119/edsac as1.icg.net ip
1: rcvd OK from 205.185.197.119 ( can_recurse)
Q: as1.icg.net ip
Ans: as1.icg.net 1 day 23 hr 59 ip 170.147.45.163
Auth: icg.net 1 day 23 hr 59 ns as1.icg.net
icg.net 1 day 23 hr 59 ns as2.icg.net
Hint: as1.icg.net 1 day 23 hr 59 ip 170.147.45.163
as2.icg.net 1 day 23 hr 59 ip 170.147.45.164
1.4: sending to 170.147.45.163/as1.icg.net 119.197.185.205.in-addr.arpa ptr
1: rcvd Server failed from 170.147.45.163 ( recurse can_recurse)
Q: 119.197.185.205.in-addr.arpa ptr
1.4: sending to 170.147.45.164/as2.icg.net 119.197.185.205.in-addr.arpa ptr
1: rcvd Server failed from 170.147.45.164 ( recurse can_recurse)
Q: 119.197.185.205.in-addr.arpa ptr
baron%
[-- Attachment #2: Type: message/rfc822, Size: 4084 bytes --]
From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ndb reverse lookup
Date: Tue, 1 Jun 2004 15:25:51 +0100
Message-ID: <1ed1feb624a20a068ff048ececb23475@vitanuova.com>
assuming you're not looking for yet another new DNS type that i didn't know about,
the request
baron% ndb/dnsquery
> 205.185.197.119 ptr
isn't quite what you want if you're doing a reverse lookup.
ndb/dnsquery automatically converts an IP address to reverse-lookup form if a dns type
is not given, but you've given a type `ptr' so it doesn't do the transformation.
reverse lookup requires a special form of `name' in the domain in-addr.arpa
that is
ndb/dnsquery
205.185.197.119
will automatically generate a search for
119.197.185.205.in-addr.arpa ptr
which is what the DNS requires.
similarly
ndb/dnsdebug 205.185.197.119
will look for
119.197.185.205.in-addr.arpa ptr
automatically
1.1: sending to 128.8.10.90/d.root-servers.net 119.197.185.205.in-addr.arpa ptr
1: rcvd OK from 128.8.10.90 ( recurse)
Q: 119.197.185.205.in-addr.arpa ptr
Auth: 205.in-addr.arpa 1 day ns chia.ARIN.NET
205.in-addr.arpa 1 day ns dill.ARIN.NET
205.in-addr.arpa 1 day ns henna.ARIN.NET
205.in-addr.arpa 1 day ns indigo.ARIN.NET
205.in-addr.arpa 1 day ns epazote.ARIN.NET
205.in-addr.arpa 1 day ns figwort.ARIN.NET
205.in-addr.arpa 1 day ns ginseng.ARIN.NET
1.4: sending to 128.8.10.90/d.root-servers.net chia.arin.net ip
1: rcvd OK from 128.8.10.90 ( recurse)
Q: chia.arin.net ip
Auth: net 2 day ns A.GTLD-SERVERS.net
net 2 day ns B.GTLD-SERVERS.net
net 2 day ns C.GTLD-SERVERS.net
net 2 day ns D.GTLD-SERVERS.net
net 2 day ns E.GTLD-SERVERS.net
net 2 day ns F.GTLD-SERVERS.net
... and so on for far too long
prev parent reply other threads:[~2004-06-01 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 14:08 Brantley Coile
2004-06-01 14:25 ` C H Forsyth
2004-06-01 18:15 ` Brantley Coile [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3d1ec3991af339a661a5ce70a629e42@borf.com \
--to=bwc@coraid.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).