On 2018-11-05 14:03, Milan Sýkora wrote:
Hello Daniel,
is any chance to achieve this behavior in the superior zone
0.10.in-addr.arpa
Yes, you can play with that like:
zone 0.10.in-addr.arpa.
-----------------------
...
104/29.0 NS my.test.server.
104.0 CNAME 104.104/29.0
...
111.0 CNAME 111.104/29.0
I think there is no simple solution for that. However, I have no
experience
with reverse zone operation :-)
Daniel
or I have to always create zone 0.0.10.in-addr.arpa on
my server with
listed records? I hoped for something more automated.
Because I just want to delegate the class to another server, it seems
to be a huge adjustment in the case of another subnet/class ( /25 or
/26 ).
Best regards,
Milan
---------- Původní e-mail ----------
Od: daniel.salzman(a)nic.cz
Komu: Milan Sýkora <sykora.milan01(a)seznam.cz>
Datum: 3. 11. 2018 18:07:41
Předmět: Re: [knot-dns-users] zone delagation format?
> Hello Milan,
>
> I guess you have something like:
>
> zone 0.0.10.in-addr.arpa.
> -------------------------
> ...
> 104/29 NS my.test.server.
> 104 CNAME 104.104/29
> ...
> 111 CNAME 111.104/29
>
> zone 104/29.0.0.10.in-addr.arpa.
> --------------------------------
> ...
> 104 PTR ...
> ...
> 111 PTR ...
>
> However, you should ask a resolver (not the authoritative server) to
> get
> an expected response because of the delegation.
>
> Daniel
>
> On 2018-11-02 11:07, Milan Sýkora wrote:
>> Hello,
>>
>> could you please send me a short guide how to delegate a zone
> subnet
>> (class) to different NS.
>>
>> I have a zone i.e. 0.10.in-addr.arpa.zone
>>
>> where I would like to delegate a part of the zone 10.0.0.104/29
>> (255.255.255.248) to different NS. It includes 8 IP addresses
>> (10.0.0.104, 10.0.0.105, 10.0.0.106 .... 10.0.0.111)
>> then I create a record in the mentioned zone like
>>
>> 104/29.0.0.10.in-addr.arpa. 300 NS my.test.server.
>>
>> I tried to understand the syntax in RFC 2317
>> (
https://tools.ietf.org/html/rfc2317) but it seems to be wrongly
>> implemented from my side.
>>
>> When I tried to "dig" records I have to ask next IP address in the
> row
>> not like dig -x 10.0.0.105 bud like dig -x 10.0.0.104/29.105
>>
>> Many thanks for the clarification,
>> best regards
>> Milan.