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