> At 23:17 +0000 3/29/08, [EMAIL PROTECTED] wrote:
> >I'm going to ask this question here too.. are we talking about the DNS
> >or are we talking about an applications use of data published in the DNS?
>
> I think that this is the important question when it comes to know
> what to write.
>
> As far as DNS is concerned, "so what" if there are multiple PTR
> records, yadda, yadda, yadda. It's nothing to the protocol.
>
> I was made aware of the desire for limiting PTRs to 1 per address
> entry via traceroute. What name should be printed in the one line
> traceroute gives a hop?
>
> In general, that's the application's problem. Apps that can't handle
> multiple PTRs are the problem to me. (Why is is that weakly written
> apps point fingers at the DNS and blame troubles on DNS-being-DNS?)
>
> Perhaps this document should tell apps writers what they can
> accomplish with multiple PTRs.
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Edward Lewis +1-571-434-5468
> NeuStar
>
> Never confuse activity with progress. Activity pays more.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
Multiple PTR records do not scale.
Today we have reverse lookups that fail because people
followed this path and exceeded the 64K DNS message size
of TCP.
When people have a 100 thousand virtual domains on a
box you just can't have PTR records for all of them.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
