From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1ed1feb624a20a068ff048ececb23475@vitanuova.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] ndb reverse lookup From: C H Forsyth Date: Tue, 1 Jun 2004 15:25:51 +0100 In-Reply-To: <4394d1765d78b94f53fa5034ccb289de@borf.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 8e4ab4e2-eacd-11e9-9e20-41e7f4b1d025 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