[146181] in North American Network Operators' Group
Re: Performance Issues - PTR Records
daemon@ATHENA.MIT.EDU (sthaug@nethelp.no)
Mon Nov 7 08:48:42 2011
Date: Mon, 07 Nov 2011 14:46:48 +0100 (CET)
To: bjorn@mork.no
From: sthaug@nethelp.no
In-Reply-To: <87ty6g1l4n.fsf@nemi.mork.no>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> > The practice of filling out the reverse zone with fake PTR record
> > started before there was wide spread support for UPDATE/DNS. There
> > isn't any need for this to be done anymore. Machines are capable
> > of adding records for themselves.
>
> How do I setup this for DHCPv6-PD? Say, I delegate 2001:db8:42::/48 to
> the end user. Should I delegate reverse DNS as well? If so, to whom?
>
> Or is it the CPEs responibility to dynamically add records for whatever
> addresses it sees on the internal LAN(s)? Are there CPEs capable of
> doing this?
>
> Or will the end systems themselves do the update against my DNS server?
> If so, how do I authenticate that?
With my ISP hat on, I find the idea of customer CPEs updating their
own PTR records to be completely unacceptable. So I guess I'll either
live without the reverse DNS, or use a name server that can synthesize
answers on the fly.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
