From nanog-bounces+bonomi=mail.r-bonomi.com@nanog.org Sun Nov 6 19:58:58 2011 Date: Sun, 6 Nov 2011 19:57:51 -0600 Subject: Re: Performance Issues - PTR Records From: Jimmy Hess <mysidia@gmail.com> To: Mark Andrews <marka@isc.org> Cc: nanog@nanog.org
On Sun, Nov 6, 2011 at 7:10 PM, Mark Andrews <marka@isc.org> wrote:
MacOS and Windows can both populate the reverse zone for you as can dhcp servers. The practice of filling out the reverse zone with fake PTR record [...]
OK.. let's say you're a DSL provider. Are you going to have your DHCP server populating the forward and reverse DNS? With what, the account holder's name? somename.example.com ?
I'll suggest that (a) IF the addresses do migrate among different customers of the ISP, (b) the addresses handed out are publicly routable, AND (c) the CPE has to 'authenticate' itself to the head-end, then it is _very_ useful *to*the*ISP* to have dynamically-assigned DNS records of the form: cust.{accountid}.{locationid}.ISP.{com/net/TLD} or something of the sort. Something of that sort can save a -lot- of time/effort in identifying the customer involved in a complaint.