On 07/11/2011, at 12:46 PM, Robert Bonomi wrote: >> 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.
Surely that's only useful if they're still allocated the address at the time of investigating said complaint; a dynamically updating DNS record like this is really no substitution for accurate accounting records in your RADIUS system. Tom