> Draft Policy ARIN-2014-6 > Remove 7.1 > > Date: 29 January 2014 > > Problem Statement: > > 7.1 attempts to assert rules on rDNS management at ARIN. It fails to > do so because it only addresses in-addr.arpa (missing equally > important rules in ip6.arpa). It's also not based on any RFC; it's an > arbitrary decision made by ARIN technical staff. We should remove this > text from policy, as it represents operational practice rather than > ARIN number policy. > > Policy statement: > > Remove 7.1 > > Comments: > a.Timetable for implementation: Immediate > b.Anything else: > > 7.1. Maintaining IN-ADDRs > > All ISPs receiving one or more distinct /16 CIDR blocks of IP > addresses from ARIN will be responsible for maintaining all > IN-ADDR.ARPA domain records for their respective customers. For blocks > smaller than /16, and for the segment of larger blocks smaller than > /16, ARIN can maintain IN-ADDRs. >
At this time I'm opposed to this policy. While I agree this text is out of date and probably should be updated. I don't necessarily agree that the section should just be removed. Reverse DNS is an important part of the services that ARIN provides to address holders. I believe that it is wholly appropriate for the NRMP to contain a section describing how ARIN should implement rDNS services to address holders. Andrew _______________________________________________ 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.
