The APNIC Whois Database Introduction and Usage. whois.apnic.net whois.ripe.netwhois.arin.net Server Unix Client ‘X’ Client Command Prompt / Web Interface.

Slides:



Advertisements
Similar presentations
Protecting Resource Records in APNIC Whois Database Database SIG APNIC-16, Seoul August 2003 Sanjaya
Advertisements

APNIC Internet Routing Registry Routing SIG APNIC-15, Taipei 26 February 2003.
1 Dynamic DNS. 2 Module - Dynamic DNS ♦ Overview The domain names and IP addresses of hosts and the devices may change for many reasons. This module focuses.
Handling Internet Network Abuse Reports at APNIC 21 October 2010 LAP-CNSA Workshop, Melbourne George Kuo.
Save Vocea/ Sanjaya - APNIC PacINET November 2002, Fiji APNIC Whois Tutorial.
Sweeping lame DNS reverse delegations APNIC16 – DNS Operations SIG Seoul, Korea, 20 August 2003.
1 prop-018-v001 Protecting historical records in the APNIC Whois Database Project Update DB SIG APNIC18 2 September 2004 Nadi, Fiji Sanjaya, Project Manager,
Domain Name System. DNS is a client/server protocol which provides Name to IP Address Resolution.
Welcome! APNIC Members Training Course Internet Resource Management I 27 April 2004, Melbourne.
Reverse DNS.
The Domain Name System. CeylonLinux DNS concepts using BIND 2 Hostnames IP Addresses are great for computers –IP address includes information used for.
APNIC Internet Routing Registry An introduction to the IRR TWNIC Meeting, 3 December 2003 Nurani Nimpuno, APNIC.
Welcome! APNIC Members Training Course Internet Resource Management II 27 March 2004, Rawalpindi, Pakistan Sponsored by NUST Institute of Information Technology.
Welcome! APNIC Members Training Course Internet Resource Management II 17 July 2003, Mumbai, India Sponsored by Reliance Infocomm Ltd.
Hands-On Microsoft Windows Server 2003 Networking Chapter 6 Domain Name System.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 8: Managing and Troubleshooting DNS.
Welcome! APNIC Members Training Course Internet Resource Management Essentials 20 October 2003, Kuala Lumpur, Malaysia In conjunction with the 1 st ASEAN.
Domain Name System: DNS
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 7: Planning a DNS Strategy.
APNIC Training Internet Resource Management Essentials June 2007, Ulaanbaatar, Mongolia Hosted by DATACOM.
Reverse DNS. Overview Principles Creating reverse zones Setting up nameservers Reverse delegation procedures.
Reverse DNS Delegations, Templates and RWS Andy Newton Chief Engineer.
Local Internet Registries. Training Course. 1 Welcome to the IP Tutorial 26 January 2001 RIPE Network Co-ordination Centre
Local Internet Registries. Training Course. 1 Welcome to the Local Internet Registry Course RIPE Network Co-ordination Centre NEW version.
Anne Lord & Mirjam Kühne. AfNOG Workshop, 10 May The whois Database Introduction and Usage.
Providing A Subset of Whois Data Via DNS Shuang Zhu Xing Li CERNET Center.
Local Internet Registries. Training Course. 1 Welcome to the Local Internet Registry Course RIPE Network Co-ordination Centre NEW version.
NATO Advanced Networking Workshop. Ljubljana, 19 September “How to Run a Local Internet Registry” or all your IPs are belong.
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E Database SIG APNIC Database Privacy Issues 1 March 2001 APRICOT, Malaysia Fabrina.
1 APNIC reverse DNS management roadmap DNS operations SIG, APNIC 21 2 March 2006.
Database Update Paul Palse Database Manager, RIPE NCC.
Part 2.
DNS Concepts APNIC 16, Seoul, Korea 19, August 2003.
70-291: MCSE Guide to Managing a Microsoft Windows Server 2003 Network Chapter 6: Name Resolution.
October 8, 2015 University of Tulsa - Center for Information Security Microsoft Windows 2000 DNS October 8, 2015.
Welcome! APNIC Members Training Course Internet Resource Management Essentials 31 August 2004, Nadi, Fiji APNIC -18 Open Policy Meeting.
IP address Allocation & and Requests AfNOG Workshop, May 2004 Dakar, Senegal.
NATO Advanced Networking Workshop. Ljubljana, 19 September RIPE whois Database RIPE Network Coordination Centre.
1 Use role objects …to maintain your contacts in APNIC whois.
Status report on Lame Delegations (work in progress) George Michaelson DB SIG APNIC17/APRICOT 2004 Feb KL, Malaysia.
REST & Relax: The future of Whois and Templates at ARIN Andy Newton, Chief Engineer.
2016 Services Roadmap APNIC Services George Kuo 9 September 2015 Jakarta.
Consultation on Policy Documentation Adam Gosling APNIC 40 Policy SIG 10 September 2015.
Welcome! APNIC Members Training Course Internet Resource Management Essentials November 2003, Beijing, China Sponsored by CNNIC.
Configuring Name Resolution and Additional Services Lesson 12.
REVERSE DNS Why and how AFRINIC-II Maputo,Mozambique 26 April 2005 Alain AINA.
1 To Insert AS Origin field into APNIC IP address database Xing Li Shuang Zhu CERNET
Andrei Robachevsky. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 1 New Version of the RIPE Database Andrei Robachevsky.
Whois Domain Object Authorisation APNIC18 – DB SIG Nadi, Fiji 2 September 2004.
MyAPNIC Survey 2015 What have we learned? APNIC Services Vivek Nigam 9 September 2015 Jakarta.
Database Tutorial 3 September, Kitakyushu, Japan 14 th APNIC Open Policy meeting APNIC.
Andrei Robachevsky. 12th APNIC Open Plicy Meeting, August 2001, Taipei, Taiwan. 1 New Version of the RIPE Database Andrei Robachevsky.
Local Internet Registries. RIPE 47 - IP Request Tutorial. 1 Welcome to the RIPE NCC IP Request Tutorial January 27, 2003 RIPE Network.
APNIC Internet Routing Registry Tutorial Seoul 19 August 2003.
OPTION section It is the first section of the named.conf User can use only one option statement and many option-value pair under the section. Syntax is.
APNIC abuse procedures Network abuse BOF. Types of abuse reported Spam Hacking Viruses Identity/credit card fraud Threats and stalking.
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E APNIC Open Address Policy Meeting APNIC Reverse DNS October 26th, Brisbane Bruce.
17 th APNIC Open Policy Meeting APNIC IPv6 Address Guidelines Akira Nakagawa )/ POWEREDCOM Billy MH Cheon / KRNIC Toshiyuki.
APNIC LAME NS measurements. Overview Methodology Initial outcomes from 128 days runtime How bad is the problem? LAME-ness trends Proposals for dealing.
Aug 2008 KRNIC of NIDA KRNIC Updates.
1 To Insert AS Origin field into APNIC IP address database Xing Li Shuang Zhu CERNET
RIPE 47: IPv6 WG 27 January 2004 Hotel Krasnapolsky, Amsterdam Jeroen Massar IPv6 Golden Networks.
1 FRED – open source registry system CZ.NIC, z.s.p.o. Jaromír Talíř
Whois Update Guangliang Pan. Overview Differences between APNIC and RIPE Whois Databases Change mnt-by from member’s maintainer to APNIC-HM for aut-num.
Lame DNS Server Sweeping
APNIC Open Policy Meeting
RIPE Whois Database Software Recent Changes
A Proposal to Protect Historical Records in APNIC Whois Database
Windows Name Resolution
Presentation transcript:

The APNIC Whois Database Introduction and Usage

whois.apnic.net whois.ripe.netwhois.arin.net Server Unix Client ‘X’ Client Command Prompt / Web Interface Windows Client HTTP/CGIClient WHOIS Queries & responses DB Intro Database - architecture

Object types OBJECT PURPOSE personcontact persons rolecontact groups/roles inetnumIPv4 addresses inet6numIPv6 addresses aut-numAutonomous System number domainreverse domains routeprefixes being announced mntner(maintainer) data protection Etc. etc. DB Intro

Object templates whois -t person: [mandatory] [single] [primary/look-up key] address: [mandatory] [multiple] [ ] country: [optional] [single] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] [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: country: phone: fax-no: nic-hdl: mnt-by: changed: source: Attributes Values Ky Xander ExampleNet Service Provider 2 Pandora St Boxville Wallis and Futuna Islands WF KX17-AP MAINT-WF-EX APNIC DB Intro

Inetnum object example –Contain IP address allocations / assignments inetnum: netname: descr: country: admin-c: tech-c: mnt-by: mnt-lower: changed: status: source: CCNEP-NP-AP Communication & Communicate Nepal Ltd VSAT Service Provider, Kathmandu NP AS75 -AP AS75-AP APNIC-HM MAINT-NP-ARUN ALLOCATED PORTABLE APNIC Attributes Values DB Intro

Inter-related objects inetnum: – … admin-c: KX17-AP tech-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 Web interface – Look-up keys –usually the object name –Check template for look-up keys DB Intro

% whois % whois zu3-ap % whois “zane ulrich” DB Intro person: Zane Ulrich address: ExampleNet Service Provider address: 2 Pandora St Boxville address: Wallis and Futuna Islands country: WF phone: fax-no: nic-hdl: ZU3-AP mnt-by: MAINT-WF-EX changed: source: APNIC Database query - UNIX

Database query - web Query the APNIC Whois Database 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 % whois SINGNET-SG % whois /19 inetnum: netname: SINGNET-SG descr: Singapore Telecommunications Ltd descr: 31, Exeter Road, #02-00, Podium Block descr: Comcentre, 0923 country: SG admin-c: CWL3-AP tech-c: CWL3-AP mnt-by: APNIC-HM changed: 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: – /20 inetnum: – /8 Database query - inetnum /25 inetnum: whois -L /20 whois /20 whois –m /20 inetnum: /26 inetnum: /24 More specific  (= smaller blocks) Less specific  (= bigger block) DB query

Whois domain object domain: in-addr.arpa descr: in-addr.arpa zone for in-addr.arpa admin-c: DNS3-AP tech-c: DNS3-AP zone-c: DNS3-AP nserver: ns.telstra.net nserver: rs.arin.net nserver: ns.myapnic.net nserver: svc00.apnic.net nserver: ns.apnic.net mnt-by: MAINT-APNIC-AP mnt-lower: MAINT-DNS-AP changed: source: APNIC

Reverse delegation procedures Complete the documentation 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 ) Please wait while your request is processed. Parsing and validating your submission … Errors encountered Your 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 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 results Connection closed. % Rights restricted by copyright. See Update FAILED: [domain] in-addr-arpa domain: in-addr.arpa descr: in-addr.arpa zone for /16 admin-c: DNS3-AP tech-c: DNS3-AP zone-c: DNS3-AP nserver: ns.apnic.net nserver: svc00.apnic.net mnt-by: MAINT-AP-DNS-DEFAULT changed: source: 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 Update OK: [domain] in-addr.arpa Processing completed. Update ok!

Questions ?