On Wed, Jan 29, 2014 at 10:27 AM, ARIN <[email protected]> wrote: > On 24 January 2014 the ARIN Advisory Council (AC) accepted "ARIN-prop-197 > Remove 7.2 Lame Delegations" as a Draft Policy. > > ARIN will actively identify lame DNS name server(s) for reverse address > delegations associated with address blocks allocated, assigned or > administered by ARIN. Upon identification of a lame delegation, ARIN shall > attempt to contact the POC for that resource and resolve the issue. If, > following due diligence, ARIN is unable to resolve the lame delegation, ARIN > will update the Whois database records resulting in the removal of lame > servers.
Howdy, Two decades of software improvements later, is there a *technical* need for ARIN to take any action at all with respect to lame delegations? Any stable DNS resolver has to deal with routine lame delegations in the forward DNS anyway. On a related note, does anyone actually make use of section 7.1, allowing an organization with less than a /16 to have ARIN handle all its RDNS rather than delegating it? How does that work? What are the mechanics involved in a registrant having ARIN set and change RDNS PTR records for him? I'm wondering if there's a good reason to keep any part of section 7 at all. Regards, Bill Herrin -- William D. Herrin ................ [email protected] [email protected] 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004 _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
