Question about dynamic IPv6-PTR-Generation

Tom tomtux007 at
Fri Aug 26 09:51:36 UTC 2016

Many thanks for your quick feedback.

This is the configuration-option, where I'm searching for. But probably 
this will take some time, until it's accepted, tested, 
implemented...etc. What do you propose in the meantime instead of using 
wildcards or allow the clients to register themselves or making static 
PTR-entries? How does other companies handle this issue?

Kind regards,


On 08/26/2016 09:17 AM, Woodworth, John R wrote:
>> Hi list
>> I'm searching a way to respond to IPv6-PTR-Queries like the "$GENERATE"
>> -mechanism for IPv4 has done it.
>> I read about Delegation, self-registration with "tcp-self" or using
>> Wildcards with the disadvantage, that every query has the same response.
>> Is there a (planned) way, to generate reverse-responses "on-the-fly"
>> with bind? I'm using the latest bind (9.10.4-P2).
> Tom,
> ** Full disclosure:  I am directly involved in the Internet-Draft (I-D)
> referenced in the below response.
> Although this does not necessarily help you today, some colleagues and I
> are working on a new standard which addresses this problem in a more
> general way by introducing a new RR type.  It provides several features
> beyond simply extending the $GENERATE directive to enormous proportions
> such as: allowing AXFR transfers of the "intent" of BULK record
> generation.  If you are interested in learning more about this, please
> follow the link in my signature below.
> We appreciate any comments/ suggestions regarding this draft.
> Regards,
> John
> --
> John Woodworth                          CenturyLink, Inc.
>    Q. Can a $GENERATE work for DNS on a /64 of reverse??
>    A. BULK CAN
> [ ]
>> Many thanks for your help.
>> Kind regards,
>> Tom
>> _______________________________________________
>> Please visit to
>> unsubscribe from this list
>> bind-users mailing list
>> bind-users at
> This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

More information about the bind-users mailing list