Reverse IPv6

Bob Harold rharolde at umich.edu
Fri Feb 3 20:14:51 UTC 2017


On Thu, Feb 2, 2017 at 5:44 AM, Cathy Almond <cathya at isc.org> wrote:

>
>
> On 02/02/2017 02:52, Filho Arrais wrote:
> > Hi,
> >
> > Hello,
> > Excuse me the question, is there anything native to IPv6 like in IPv4
> > for PTR input?
> >
> > $GENERATE 1-254 $  PTR   100.200.236.$.examplae.com <http://examplae.com
> >.
> >
> > --
>
> Bear in mind that that reverse populating your IPv6 space in entirety is
> potentially going to hurt you (the $GENERATE command actually generates
> an RR for each record which will be held in the zone in memory).  Think
> about how many records your $GENERATE is going to create.  You don't
> want to have named failing to start because it does not have enough
> memory (or the machine on which it is running does not have enough
> memory) to hold all of the PTR RRsets in the zone.
>
> Please also think about whether you need to do this or not, especially
> as the names are going to follow a generic pattern and not provide any
> useful intelligence about the host using that address.
>
> Instead, I would suggest that you just create PTR entries for the IPv6
> hosts that actually need them for some reason, or to use dynamic DNS to
> add/replace/delete them as addresses are used/discarded by dynamic clients.
>

Note that there is future work being done to solve the 'too many entries'
issue with GENERATE (does not solve the other concerns):
https://www.ietf.org/internet-drafts/draft-woodworth-bulk-rr-03.txt

-- 
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20170203/5e156bcd/attachment.html>


More information about the bind-users mailing list