On 5/3/16, 5:00 AM, "Stephane Bortzmeyer" <bortzme...@nic.fr> wrote:
>On Mon, May 02, 2016 at 08:59:45PM +0000, > Howard, Lee <lee.how...@twcable.com> wrote > a message of 289 lines which said: > >> Having forward and reverse match isn't BCP (Stephane Bortzmeyer, and >> others) > >No, that was not my point. My point was that having a PTR isn't >BCP. _If_ there is a PTR, it's certainly better if the A/AAAA and the >PTR match. Ah, thank you for clarifying. I think there are a few people who think that having a PTR is a BCP. Not a majority, but I'm not sure it's "in the rough" of consensus. Would it be sufficient for me to say it's "debatable"? OLD: Best practice is that "Every Internet-reachable host should have a name" [RFC1912] that is recorded with a PTR resource record in the .ARPA zone, and "PTR's should use official names and not aliases" [RFC1033]. Some network services perform a PTR lookup on the source address of incoming packets before performing services. NEW: RFC 1912 recommended that "every internet-reachable host should have a name" and says "Failure to have matching PTR and A records can cause loss of Internet services similar to not being registered in the DNS at all." While the need for a PTR record and for it to match is debatable as a best practice, some network services still do perform a PTR lookip on the source address of incoming connections and verify that the PTR and A records match before providing service. I could also link to the "Five common uses for PTR lookups" in the "Considerations and Recommendations" section. Lee ________________________________ This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
