the apnic whois database introduction and usage. whois.apnic.net whois.ripe.netwhois.arin.net server...
TRANSCRIPT
The APNIC Whois Database
Introduction and Usage
whois.apnic.net whois.ripe.net whois.arin.net
ServerServer
Unix ClientUnix Client ‘‘X’ ClientX’ Client
Command Prompt / Web InterfaceCommand Prompt / Web Interface
Windows ClientWindows Client
HTTP/CGI
ClientClient
WHOIS Queries & responses
DB Intro
Database - architecture
Object types
OBJECT PURPOSE
person contact persons
role contact groups/roles
inetnum IPv4 addresses
inet6num IPv6 addresses
aut-num Autonomous System number
domain reverse domains
route prefixes being announced
mntner (maintainer) data protection
Etc. etc.
DB Intro
http://www.apnic.net/db/
Object templates
whois -t <object type>
person: [mandatory] [single] [primary/look-up key]address: [mandatory] [multiple] [ ]country: [optional] [single] [ ]phone: [mandatory] [multiple] [ ]fax-no: [optional] [multiple] [ ]e-mail: [mandatory] [multiple] [look-up key]nic-hdl: [mandatory] [single] [primary/look-up key]remarks: [optional] [multiple] [ ]notify: [optional] [multiple] [inverse key]mnt-by: [mandatory] [multiple] [inverse key]changed: [mandatory] [multiple] [ ]source: [mandatory] [single] [ ]
% whois -h whois.apnic.net -t person
To obtain template structure*, use :
DB Intro
*Recognised by the RIPE whois client/server
Person object example
– Person objects contain contact information
person:
address:
address:address:
country:phone:
fax-no:
e-mail:
nic-hdl:mnt-by:
changed:source:
Attributes Values
Ky XanderExampleNet Service Provider2 Pandora St BoxvilleWallis and Futuna IslandsWF+680-368-0844+680-367-1797kxander@[email protected] 20020731APNIC
DB Intro
Inetnum object example
– Contain IP address allocations / assignments
inetnum:netname:descr:descr:country:admin-c:tech-c:mnt-by:mnt-lower:changed:status: source:
202.51.64.0 - 202.51.95.255 CCNEP-NP-APCommunication & Communicate Nepal Ltd
VSAT Service Provider, Kathmandu NPAS75-APAS75-APAPNIC-HMMAINT-NP-ARUN [email protected] 20010205ALLOCATED PORTABLEAPNIC
Attributes Values
DB Intro
Inter-related objects
inetnum:202.64.10.0 – 202.64.10.255
…admin-c: KX17-APtech-c: ZU3-AP…mnt-by: MAINT-WF-EX
…
IPv4 addresses
person:…
nic-hdl: ZU3-AP
…
Contact info
person:…
nic-hdl: KX17-AP
…
Contact info
mntner:MAINT-WF-EX
……
Data protection
DB Intro
Basic database queries
• Unix – whois –h whois.apnic.net <lookup key>
• Web interface– http://www.apnic.net/apnic-bin/whois2.pl
• Look-up keys – usually the object name– Check template for look-up keys
DB Intro
% whois [email protected]
% whois zu3-ap% whois “zane ulrich”
DB Intro
person: Zane Ulrichaddress: ExampleNet Service Provideraddress: 2 Pandora St Boxvilleaddress: Wallis and Futuna Islandscountry: WFphone: +680-368-0844fax-no: +680-367-1797e-mail: [email protected]: ZU3-APmnt-by: MAINT-WF-EXchanged: [email protected] 20020731source: APNIC
Database query - UNIX
Database query - web
Query the APNIC Whois Database
http://www.apnic.net/apnic-bin/whois2.pl
2.Search options(flags)
1.Type in search key
3. ‘Search Whois’
DB Intro
Database query - inetnum
• Note• Incomplete addresses padded with “.0”• Address without prefix interpreted as “/32”
% whois 203.127.128.0 - 203.127.159.255
% whois SINGNET-SG% whois 203.127.128.0/19
inetnum: 203.127.128.0 - 203.127.159.255netname: SINGNET-SG descr: Singapore Telecommunications Ltd descr: 31, Exeter Road, #02-00, Podium Blockdescr: Comcentre, 0923 country: SGadmin-c: CWL3-APtech-c: CWL3-APmnt-by: APNIC-HM changed: [email protected] 19990803 source: APNIC
DB Intro
Advanced database queries
– Flags used for inetnum queries
None find exact match
- l find one level less specific matches
- L find all Less specific matches
- m find first level more specific matches
- M find all More specific matches
- x find exact match
- d enables use of flags for reverse domains
- r turn off recursive lookups
DB query
inetnum: 202.64.0.0 – 202.64.15.255
202.64.0.0/20
inetnum:
202.0.0.0 – 202.255.255.255
202.0.0.0/8
Database query - inetnum
202.64.12.128/25
inetnum:
whois -L 202.64.0.0 /20
whois 202.64.0.0 /20
whois –m 202.64.0.0 /20 inetnum:
202.64.15.192/26
inetnum:
202.64.10.0/24More specific (= smaller blocks)
Less specific (= bigger block)
DB query
Whois domain object
domain: 28.12.202.in-addr.arpadescr: in-addr.arpa zone for 28.12.202.in-addr.arpaadmin-c: DNS3-APtech-c: DNS3-APzone-c: DNS3-APnserver: ns.telstra.netnserver: rs.arin.netnserver: ns.myapnic.netnserver: svc00.apnic.netnserver: ns.apnic.netmnt-by: MAINT-APNIC-APmnt-lower: MAINT-DNS-APchanged: [email protected] 19990810source: APNIC
Reverse delegation procedures
• Complete the documentation• http://www.apnic.net/db/domain.html
• On-line form interface– Real time feedback– Gives errors, warnings in zone
configuration• serial number of zone consistent across
nameservers• nameservers listed in zone consistent
– Uses database ‘domain’ object
Online errors (also via email)
Please wait while your request is processed.Parsing and validating your submission …
Errors encounteredYour update request was unable to be completed due to the following errors. Please correct them and try again. If the error is temporary in nature, correct the error and ‘Reload’ this page (possibly this frame).
• *ERROR*. SOA on “ns.apnic.net” does not match SOA on “svc00.apnic.net”. All nservers must respond with the same SOA.
• *ERROR*. NS RR for ns.telstra.net found on svc00.apnic.net but not in supplied template.
• *ERROR*. NS RR for ns.telstra.net found on svc00.apnic.net but not in supplied template.
• *ERROR*. NS RR for ns.telstra.net found on ns.apnic.net but not in supplied template.
• *ERROR*. NS RR for ns.telstra.net found on ns.apnic.net but not in supplied template.
• *ERROR*. cross-check of listed NS RR failed.
Request submission error
Verifying your authorisation ….Your maintainer uses the ‘CRYPT-PW’ or ‘NONE’ authorisation schema. Attempting to submit your request directly to the database. Update resultsConnection closed.
% Rights restricted by copyright. See http://www.apnic.net/db/dbcopyright.htmlUpdate FAILED: [domain] 174.202.in-addr-arpa
domain: 174.202.in-addr.arpadescr: in-addr.arpa zone for 202.174/16admin-c: DNS3-APtech-c: DNS3-APzone-c: DNS3-APnserver: ns.apnic.netnserver: svc00.apnic.netmnt-by: MAINT-AP-DNS-DEFAULTchanged: [email protected] 20000215source: APNIC*ERROR*: authorisation failed, request forwarded to maintainer
Processing completed
Update failed
Authorisation failed
Successful update
Please wait while your request is processed.
Parsing and validating your submission …
Warnings generated• Verifying your authorisation …. Your maintainer uses the ‘CRYPT-PW’ or ‘NONE’ authorisation schema. Attempting to submit your request directly to the database.
Update results
Connection closed.% Rights restricted by copyright. See http://www.apnic.net/db/dbcopyright.htmlUpdate OK: [domain] 174.202.in-addr.arpa
Processing completed.
Update ok!
Questions ?