[arin-ppml] Draft Policy ARIN-2014-5: Remove 7.2 Lame Delegations

Andrew Dul andrew.dul at quark.net
Mon Feb 3 10:56:01 EST 2014

On 1/29/2014 4:18 PM, William Herrin wrote:
> On Wed, Jan 29, 2014 at 10:27 AM, ARIN <info at arin.net> 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
It would be helpful for this discussion if ARIN staff could produce a
brief statement on the current state of how this section has been
implemented within ARIN's operational procedures.  I assume some of this
will come later with the staff assessment, but a limited response might
be helpful for the community to understand how this change would effect
ARIN's current operational procedures.


More information about the ARIN-PPML mailing list