Lame delegation status report DNS operations SIG APNIC19 24 February 2005, Kyoto, Japan.
Download ReportTranscript Lame delegation status report DNS operations SIG APNIC19 24 February 2005, Kyoto, Japan.
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 Status NS Disabled by Domain Admin Total NS In 15 day period In 45 day period Disabled by APNIC Nameservers Domains 0 (future use) 168,042 61,963 12,471 9,571 11,544 6,982 0 0 Status as of 15/02/2005 Status NS Disabled by Domain Admin Total NS In 15 day period Namservers Domains 0 143,697 14,481 (future use) 64,850 9,500 In 45 day period 9,040 5,547 Disabled by APNIC 1,107 807 Policy effectiveness Policy implementation in-addr.arpa domains 70000 60000 No. 50000 T O T AL Va lid La m e 40000 30000 Member initiated fix 20000 10000 0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 05 05 05 05 08 08 08 08 09 09 09 10 10 10 11 11 11 12 12 12 01 01 01 02 01 11 21 31 10 20 30 10 20 30 09 19 29 09 19 29 08 18 28 07 Dat e Date 20050208 20050131 20050123 20050115 20050107 20041230 20041222 20041214 20041206 20041128 20041120 20041112 20041104 20041027 20041019 20041011 20041003 20040925 20040917 20040909 20040901 20040824 20040816 20040808 Date % Policy effectiveness Policy implementation Ratio of lameness 100 90 80 70 60 50 40 Va lid La m e 30 20 10 0 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 – 18.66% on 01/08/04 – 16.34% on 15/02/05 • Ongoing process – Consider time to affect a change is 60 days – APNIC continually monitoring • IPv6 yet to be included • Policy appears well received Questions?