Hello Tom

I only know of Knot having a feature available for this use case:

https://www.knot-dns.cz/docs/2.x/html/configuration.html#synth-record-automatic-forward-reverse-records

Daniel

On 26.08.16 11:51, Tom wrote:
> 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,
> 
> Tom
> 
> 
> 
> 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
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to