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 [thread overview]
Message-ID: <1ed1feb624a20a068ff048ececb23475@vitanuova.com> (raw)
In-Reply-To: <4394d1765d78b94f53fa5034ccb289de@borf.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
next prev parent reply other threads:[~2004-06-01 14:25 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 [this message]
2004-06-01 18:15 ` Brantley Coile
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=1ed1feb624a20a068ff048ececb23475@vitanuova.com \
--to=forsyth@vitanuova.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).