Lame delegation status report

Slides:



Advertisements
Similar presentations
1 [prop-054] Revision of APNIC-103-v001 NIR SIG 27 February 2008 APNIC 25, Taipei George Michaelson.
Advertisements

Managing IP addresses for your private clouds 2013 ASEAN CAS Summit Bangkok, Thailand 7 February 2013 George Kuo Member Services Manager.
APNIC Member Services George Kuo. MyAPNIC 2 What is MyAPNIC A secure Member services website Internet resources management, for example: –Whois updates.
Sweeping lame DNS reverse delegations APNIC16 – DNS Operations SIG Seoul, Korea, 20 August 2003.
1 [prop-038] Proposal to amend APNIC Lame DNS reverse delegation policy Policy SIG 7 Sep 2006 APNIC 22, Kaohsiung, Taiwan Terry Manderson.
Network security policy: best practices
Implementation Update Adam Gosling APNIC Policy SIG Meeting Thursday, 18 September 2014.
Status report on Lame Delegations (work in progress) George Michaelson DB SIG APNIC17/APRICOT 2004 Feb KL, Malaysia.
APNIC Status Report ARIN X Eugene, Oregon Oct 30-Nov 1, 2002.
Prop-080: Removal of IPv4 Prefix Exchange Policy Guangliang Pan Resource Services Manager, APNIC.
Developing IPv6 Address Guidelines Izumi Okutani Japan Network Information Center Address Policy SIG Aug 2003, Seoul.
Network Abuse Update Frank Salanitri Project & Systems Services Manager, APNIC.
Sweeping Lame DNS Delegations A Proposal DNS OPS SIG APNIC 15, Taipei, Taiwan 26 February 2003.
Copyright (c) 2006 Japan Network Information Center Survey results in JP on IPv6 assignment size Izumi Okutani Japan Network Information Center (JPNIC)
1 Lame delegation status report DNS Operations SIG APNIC , Hanoi.
IPv4 IXP Address Policy APNIC Policy SIG Meeting Taipei, August 2001 Philip Smith.
APNIC abuse procedures Network abuse BOF. Types of abuse reported Spam Hacking Viruses Identity/credit card fraud Threats and stalking.
APNIC Status Report RIPE 44 Amsterdam, The Netherlands January 27-31, 2003.
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.
Prop-073 Automatic allocation/assignment of IPv6 Terry Manderson Andy Linton.
1 Welcome to the Policy SIG Policy SIG 1 March 2007 APNIC 23, Bali, Indonesia Kenny Huang.
APNIC Update Elly Tawhai Senior Internet Resource Analyst/Liaison Officer, Pacific, APNIC AusNOG
Policy SIG Report APNIC AGM Friday 29 August 2008 Christchurch, New Zealand 1.
1 Welcome to the Policy SIG 6 Sep 2006 APNIC 22, Kaohsiung, Taiwan.
1 DNS Operations SIG Report Joe Abley, ISC APNIC 18 Nadi, Fiji, September 2004.
Implementation Of Lame Delegation Policy
Implementation of ARIN's Lame DNS Delegation Policy
Whois Data Privacy Issues in Japan
Research & Liaison Officer (Pacific)
A proposal to deprecate ip6.int reverse DNS service in APNIC
Update on Implementation of Proposed Rates for CII Customers; Outreach
Lame DNS Server Sweeping
APNIC Open Policy Meeting
Member Services Report
LACNIC IV Santiago, Chile April, 2003
APNIC Status Report RIPE 34
DNS as a Service ccTLD Constituency
Wharton Audit & Compliance\ January 19, 2018
Prop-093: Reducing the minimum delegation size for the final /8
APNIC 29 Policy SIG report
IPv6 Allocation Status Report
Progress Report for ip6.int Deprecation
Sanjaya, Project Manager, APNIC Secretariat
Policy SIG Wednesday 3 March 2010
News from APNIC ARIN XXII 16 October 2008.
DNS Operations SIG Feb APNIC19, Kyoto, Japan
Policy SIG Chair Report
A week in the life of (IRT address)
Jane Zhang & Wendy Zhao Wei
Policy SIG Thursday 26 February Manila, Philippines
DNS Operations SIG APNIC , Kyoto
Randy Bush & Philip Smith
MyAPNIC Project Update
Recovery of Unused Address Space prop-017-v001
The Current Issues in IPv6 Policy
IPv4 Transfer Policy Amendments
AMM APNIC 15, Taipei, Taiwan 28 Feb 2003
Proposal to Deprecate MAIL-FROM in Maintainer Object
Overview of policy proposals
DNS operations SIG APNIC 17 Kuala Lumpur, Malaysia
Report on the NIR fee WG discussions
Proposal to Clean Up Whois Database
Status Report on Policy Implementation at the APNIC Secretariat
Status Report on Policy Implementation at the APNIC Secretariat
Database SIG APNIC19 24 February 2005, Kyoto, Japan
IPv6 Policy Update ~ APNIC community ~
APNIC Member Meeting APNIC16 Seoul, Korea
Status on “Proposal for the whois database query”
APNIC 25 Member Meeting February 29, 2008
APNIC 29 PDP BoF report Tuesday 2 March /05/10
Presentation transcript:

Lame delegation status report DNS operations SIG APNIC19 24 February 2005, Kyoto, Japan

Adopted proposal (prop-004-v001) Identify potential lameness Two points of test, AU & JP Test the DNS reverse delegation 15 day test period Attempt to notify the domain holder 45 day notice period Disable lame DNS reverse delegation If not corrected at end of notice period

Policy implementation 30/09/2004 First contact emails sent on 23/11/2004 Delay for due diligence Make sure contact is warranted and appropriate Minor teething problems First ticket (tracking) created 11:38:10 23/11/2004 First ticket resolved with nameservers fixed 30/11/2004 16:20:42 2004 (7 days) Average time to resolve issues after contact email is now 2 days. First lame nameservers undelegated 08/01/2005

Policy - technical caveats IPv6 lameness pending IPv6 islands cause issues of connectivity Some networks have interesting v6 ACLs Relatively small set of delegations at present Risk of removal for “Lab” networks

Policy - technical caveats Contact pending for: Admins responsible for 5 or more lame domains APNIC evaluating most appropriate process and methods A flood of email should be avoided Admin-c/Tech-c No. Domains EXX-AP/WXXXX-AP 385 DXXX-AP/DXXX-AP 304 PXXX-AP 256 HXXX-AP 238 NXXX-AP 227

Pre-implementation status Nameservers Domains NS Disabled by Domain Admin (future use) Total NS 168,042 61,963 In 15 day period 12,471 9,571 In 45 day period 11,544 6,982 Disabled by APNIC

Status as of 15/02/2005 Status Namservers Domains NS Disabled by Domain Admin (future use) Total NS 143,697 64,850 In 15 day period 14,481 9,500 In 45 day period 9,040 5,547 Disabled by APNIC 1,107 807

Policy implementation Policy effectiveness Policy implementation Member initiated fix

Policy implementation Policy effectiveness Policy implementation 2.32% decrease

The resolution process Reports from APNIC Hostmasters Most problems in resolution were due to: Forgotten password on resource Incorrect contacts Problems configuring a nameserver to be authoritative

Key points Reduction in lame percentage Ongoing process Consider time to affect a change is 60 days APNIC continually monitoring IPv6 yet to be included Policy appears well received

Questions?