<html>
<body>
While I don't wish to start a word war on the subject, I should like to
note that<br>
there are other applications besides MTAs which provide capabilities
which depend<br>
upon the existence of PTR records, and even PTR/A matching, under IPv4,
and that will<br>
expect to be able to do so under IPv6. A case in point is
SSHd. Many of the other<br>
sites running SSHd to which my customers connect are using versions of
SSHd which<br>
stall and time-out if PTR records for my client-side IPs are not
available. Further,<br>
a sizeable fraction of those other sites still use hostname-based ACL
mechanisms (in<br>
spite of the long-standing stupidity of doing so). When these
connections fail or are<br>
extremely slow to connect, I get very growly customers. Therefore,
we intend to<br>
roll-out matching IPv6 AAAA/PTR records.<br><br>
<br>
At 09:16 AM 12/17/2010, Wayne MacLaurin wrote:<br>
<blockquote type=cite class=cite cite="">That's an excellent question
!<br><br>
I seem to recall a heated debate at the RIPE meeting in Rome back in
November. It would seem that most people wish PTR
was never invented and it causes more grief than its
worth. A few folks seemed to be resigned to having to
do PTR for MTAs and other services that have built-in requirements but
most would like to see the entire concept go away….<br><br>
Anybody else, who's rolling out IPv6 on a large scale, have any comments
?<br><br>
Wayne MacLaurin<br>
Executive Director, DNS-OARC<br>
<a href="mailto:wayne@dns-oarc.net">wayne@dns-oarc.net</a><br><br>
<br>
On 2010-12-17, at 10:02 AM, R.P. Aditya wrote:<br><br>
<blockquote type=cite class=cite cite="">I like to question my habits --
the current one: while getting ready to<br>
roll out IPv6, whether to bother with PTR records at all, and if so,<br>
whether to just automatically generate them (except maybe for MTAs)
and<br>
not bother to match the forwards (so far, I'm not convinced either
way<br>
and given the pace of the rollout, time can tell).<br><br>
R.P. (Adi) Aditya<br>
Network Architect<br>
ITSComm Network Engineering<br>
University of Michigan<br>
+1 (734) 330-2499<br>
<a href="mailto:rpaditya@umich.edu">rpaditya@umich.edu</a></blockquote>
<br>
_______________________________________________<br>
dns-operations mailing list<br>
dns-operations@lists.dns-oarc.net<br>
<a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations" eudora="autourl">
https://lists.dns-oarc.net/mailman/listinfo/dns-operations</a>
</blockquote>
<x-sigsep><p></x-sigsep>
--<br>
Douglas C.
Stephens
| Network/DNS/Unix/Windows Admin<br>
System Support Specialist | Email
Postmaster<br>
Information
Systems
| Phone: (515) 294-6102<br>
Ames Laboratory, US DOE |
Email: stephens@ameslab.gov<br>
</body>
</html>