> -----Original Message----- > From: dnsop-boun...@ietf.org [mailto:dnsop-boun...@ietf.org] On Behalf Of Mark > Andrews > Sent: Monday, August 31, 2009 9:53 PM > To: Doug Barton > Cc: dnsop > Subject: Re: [DNSOP] Draft on rDNS for IPv6: draft-howard-isp-ip6rdns-00 > > Windows already attempts to do UPDATE. It just does it over UDP. > Switching to TCP for the UPDATE message should be trivial.
I guess that's for them to decide, but certainly the protocols are there. I think I said that in the draft, too. > Since this is IPv6 give each customer their own address block and > corresponding reverse zone. You don't need a single big machine > to do this. Would you delegate the reverse zone to CPE, or support updates on your servers? Hm, need to filter at the edge, make sure customer's don't update each other's records. Some rate limiting, maybe. Is a matching forward zone required, too? Education needed: how do you tell a residential user what server will accept their dynamic PTR updates? Lee _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
