Is it just me or are reverse lookups just not working against IP Space? bash-2.05# whois 203.97.66.1 whois: connect(): Operation timed out Is this all dealt with via APNIC? Cheers Dan
Dan Clark wrote:
Is it just me or are reverse lookups just not working against IP Space?
bash-2.05# whois 203.97.66.1
whois: connect(): Operation timed out
Is this all dealt with via APNIC?
ARIN's whois server seems to be down currently, but you can try asking APNIC directly: $ whois -h whois.apnic.net 203.97.66.1 % [whois.apnic.net node-1] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html inetnum: 203.97.0.0 - 203.97.127.255 netname: CLEAR-NZ descr: CLEAR Communications Ltd descr: 24/7 CLEAR NOC phone +64 9 912-4990 country: NZ admin-c: CCNO1-AP tech-c: CCNO1-AP notify: netobjs(a)clear.net.nz mnt-by: MAINT-CLIX-NZ changed: netobjs(a)clear.net.nz 20010624 status: ALLOCATED PORTABLE source: APNIC role: CLEAR Communications Network Objects Maintainer address: ISP Duty Officer, CLEAR Net Operations address: CLEAR Communications Limited address: Private Bag 92143 address: Auckland country: NZ phone: +64 9 912-5024 fax-no: +64 9 912-5008 e-mail: netobjs(a)clear.net.nz admin-c: CCNO1-AP tech-c: CCNO1-AP nic-hdl: CCNO1-AP remarks: For network abuse contact abuse(a)clear.net.nz remarks: For 24/7 after-hours NOC, please call +64 9 912-4990 notify: netobjs(a)clear.net.nz mnt-by: MAINT-CLIX-NZ changed: netobjs(a)clear.net.nz 20010821 source: APNIC -- Juha
Hi Dan, Yes, the inetnum object for this range is in the APNIC whois (as Juha pointed out below), not the ARIN whois db. (I'll contact ARIN and make sure they're aware of their whois being down.) But if you don't know what whois database a range is in, you can use the -a flag to query all RIR whois databases. As for this particular reverse domain, this is what I found: The reverse domain for this range is in the whois db: --- $ whois -h whois.apnic.net -r 66.97.203.in-addr.arpa % [whois.apnic.net node-1] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html domain: 66.97.203.in-addr.arpa descr: ConceptNet country: NZ admin-c: CCNO1-AP tech-c: CCNO1-AP zone-c: CCNO1-AP nserver: ns1.concept.net.nz nserver: ns2.concept.net.nz nserver: ns3.concept.net.nz mnt-by: MAINT-CLIX-NZ changed: hm-changed(a)apnic.net 20030428 source: APNIC --- A dig on the domain shows it as being in the DNS: --- $ dig @ns.apnic.net. 66.97.203.in-addr.arpa ; <<>> DiG 9.2.1 <<>> @ns.apnic.net. 66.97.203.in-addr.arpa ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26872 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0 ;; QUESTION SECTION: ;66.97.203.in-addr.arpa. IN A ;; AUTHORITY SECTION: 66.97.203.in-addr.arpa. 172800 IN NS ns1.concept.net.nz. 66.97.203.in-addr.arpa. 172800 IN NS ns2.concept.net.nz. 66.97.203.in-addr.arpa. 172800 IN NS ns3.concept.net.nz. ;; Query time: 1 msec ;; SERVER: 203.37.255.97#53(ns.apnic.net.) ;; WHEN: Wed Jun 23 16:45:26 2004 ;; MSG SIZE rcvd: 108 --- APNIC also has a diagnostic tool to see if a given nameserver and/or zone has been set up in a consistent fashion which can be accessed here: http://www.apnic.net/apnic-bin/testns.pl The results of testing ns1.concept.net.nz and ns2.concept.net.nz gives the following result: --- Checking 'ns1.concept.net.nz/202.127.8.1' (good) 'ns1.concept.net.nz/202.127.8.1' can resolve 'ns1.concept.net.nz' (info) While checking if 'ns1.concept.net.nz/202.127.8.1' could resolve '202.127.8.1', no records were returned which exactly matched ns1.concept.net.nz or 202.127.8.1, but valid records were returned (eg, 'A', 'AAAA' or 'PTR') - possible mismatch in forward name vs reverse name. Checking 'ns2.concept.net.nz/202.127.8.2' (good) 'ns2.concept.net.nz/202.127.8.2' can resolve 'ns2.concept.net.nz' (info) While checking if 'ns2.concept.net.nz/202.127.8.2' could resolve '202.127.8.2', no records were returned which exactly matched ns2.concept.net.nz or 202.127.8.2, but valid records were returned (eg, 'A', 'AAAA' or 'PTR') - possible mismatch in forward name vs reverse name. --- - So this seems to be up and running fine! Cheers, Nurani Nimpuno APNIC
thanks for that, 203.x was just an example
Cheers
Dan
----- Original Message -----
From: "Nurani Nimpuno"
Hi Dan,
Yes, the inetnum object for this range is in the APNIC whois (as Juha pointed out below), not the ARIN whois db. (I'll contact ARIN and make sure they're aware of their whois being down.)
But if you don't know what whois database a range is in, you can use the -a flag to query all RIR whois databases.
As for this particular reverse domain, this is what I found:
The reverse domain for this range is in the whois db:
--- $ whois -h whois.apnic.net -r 66.97.203.in-addr.arpa % [whois.apnic.net node-1] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
domain: 66.97.203.in-addr.arpa descr: ConceptNet country: NZ admin-c: CCNO1-AP tech-c: CCNO1-AP zone-c: CCNO1-AP nserver: ns1.concept.net.nz nserver: ns2.concept.net.nz nserver: ns3.concept.net.nz mnt-by: MAINT-CLIX-NZ changed: hm-changed(a)apnic.net 20030428 source: APNIC ---
A dig on the domain shows it as being in the DNS:
--- $ dig @ns.apnic.net. 66.97.203.in-addr.arpa
; <<>> DiG 9.2.1 <<>> @ns.apnic.net. 66.97.203.in-addr.arpa ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26872 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0
;; QUESTION SECTION: ;66.97.203.in-addr.arpa. IN A
;; AUTHORITY SECTION: 66.97.203.in-addr.arpa. 172800 IN NS ns1.concept.net.nz. 66.97.203.in-addr.arpa. 172800 IN NS ns2.concept.net.nz. 66.97.203.in-addr.arpa. 172800 IN NS ns3.concept.net.nz.
;; Query time: 1 msec ;; SERVER: 203.37.255.97#53(ns.apnic.net.) ;; WHEN: Wed Jun 23 16:45:26 2004 ;; MSG SIZE rcvd: 108 ---
APNIC also has a diagnostic tool to see if a given nameserver and/or zone has been set up in a consistent fashion which can be accessed here: http://www.apnic.net/apnic-bin/testns.pl
The results of testing ns1.concept.net.nz and ns2.concept.net.nz gives the following result:
--- Checking 'ns1.concept.net.nz/202.127.8.1'
(good) 'ns1.concept.net.nz/202.127.8.1' can resolve 'ns1.concept.net.nz' (info) While checking if 'ns1.concept.net.nz/202.127.8.1' could resolve '202.127.8.1', no records were returned which exactly matched ns1.concept.net.nz or 202.127.8.1, but valid records were returned (eg, 'A', 'AAAA' or 'PTR') - possible mismatch in forward name vs reverse name. Checking 'ns2.concept.net.nz/202.127.8.2'
(good) 'ns2.concept.net.nz/202.127.8.2' can resolve 'ns2.concept.net.nz' (info) While checking if 'ns2.concept.net.nz/202.127.8.2' could resolve '202.127.8.2', no records were returned which exactly matched ns2.concept.net.nz or 202.127.8.2, but valid records were returned (eg, 'A', 'AAAA' or 'PTR') - possible mismatch in forward name vs reverse name. ---
- So this seems to be up and running fine!
Cheers,
Nurani Nimpuno APNIC
On 23 Jun 2004, at 09:05, Nurani Nimpuno wrote:
But if you don't know what whois database a range is in, you can use the -a flag to query all RIR whois databases.
This is a bit operating-system dependent -- on NetBSD, FreeBSD, OpenBSD and Darwin/Mac OS X, "-a" is shorthand for "-h whois.arin.net", for example. Joe
On Wed, 23 Jun 2004, Joe Abley wrote:
On 23 Jun 2004, at 09:05, Nurani Nimpuno wrote:
But if you don't know what whois database a range is in, you can use the -a flag to query all RIR whois databases.
This is a bit operating-system dependent -- on NetBSD, FreeBSD, OpenBSD and Darwin/Mac OS X, "-a" is shorthand for "-h whois.arin.net", for example.
true. should've maybe been a bit more specific with that. ;) for those who are interested, you can get the ripe whois client here: http://www.ripe.net/db/ (under software), which let's you do all sorts of fancy queries in the ripe and apnic database. cheers, nurani apnic
Joe
participants (4)
-
Dan Clark -
Joe Abley -
Juha Saarinen -
Nurani Nimpuno