Hi Jason, so if i understand it correctly, it’s up to me how fine i split the zones to send it to the dns-server – and how fast the searches can be at the end. Because we have 1900 scopes (not just devices – each scope has up to 6 devices) it would be much faster when i write zones from 32.10.in-addr.arpa up to 49.10.in-addr.arpa (and maybe going on, not knowing what the future will bring).
“how many” and “how often” meant the entries in the configuration. Thank you for your thoughts. Mit freundlichen Grüßen / With kind regards Sebastian Wessel Specialist IT Systems __________________________________________________________________________________ Sebastian Wessel Takko Holding GmbH Alfred-Krupp-Straße 21 · 48291 Telgte · Germany T +49 2504 923 865 · Mobile +49 152 21811579 · F +49 2504 923 797 www.takko.com __________________________________________________________________________________ Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser Mail erforderlich ist. Geschäftsführer: Ulrich Eickmann, Thomas Helmreich, Alexander Mattschull, Arnold Mattschull Amtsgericht Münster HRB 8939 Ust.-Id Nr. DE209094382 From: Jason Guy [mailto:[email protected]] Sent: Wednesday, February 08, 2017 4:06 PM To: Wessel, Sebastian Cc: KEA-Users ([email protected]) Subject: Re: [Kea-users] Reverse DDNS Config Hi Sebastian, I was testing with this a week ago, and what I found was the reverse domain works just like you indicate, in that if you specify it as 10.in-addr.arpa, the PTR entries will just be longer; you will see PTR entries like y.x.32, and x.y.48... Seemed like everything worked alright, though I assume the lookup time in this case may be a little longer if there are 1900 PTR entries under one reverse domain... Worse case, you create 16 reverse domains to speed up the resolution of the PTR entries... I was not sure what you meant by "how often" and "how many". Can you clarify? Jason On Wed, Feb 8, 2017 at 6:04 AM, Wessel, Sebastian <[email protected]<mailto:[email protected]>> wrote: Hello List-Members, we plan to move our dhcp server (ca. 1,900 ipv4 scopes) from Microsoft away and the kea testserver is doing very well. We also solved the forward ddns section because we have a windows ads up and running and would like to leave that in redmonds hands. Now we want to also have reverse ddns. Section 10.2.4.1 describes how – but not how often and how detailed ☺ "DhcpDdns": { "reverse-ddns": { "ddns-domains": [ { "name": "1.0.0.0.8.B.D.0.1.0.0.2.ip6.arpa.", "key-name": "", "dns-servers": [ ] } ] } } Most of the scopes are 10.32.x.y up to 10.49.x.y. What would be the best way to tell kea the reverse ddns needs? Do I just need the 10.in-addr.arpa. or do I have to split it up more detailed? The devices all have the same domain-name “example.com<http://example.com>”. Mit freundlichen Grüßen / With kind regards Sebastian Wessel Specialist IT Systems __________________________________________________________________________________ Sebastian Wessel Takko Holding GmbH Alfred-Krupp-Straße 21 · 48291 Telgte · Germany T +49 2504 923 865<tel:+49%202504%20923865> · Mobile +49 152 21811579<tel:+49%201522%201811579> · F +49 2504 923 797<tel:+49%202504%20923797> www.takko.com<http://www.takko.com> __________________________________________________________________________________ Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser Mail erforderlich ist. Geschäftsführer: Ulrich Eickmann, Thomas Helmreich, Alexander Mattschull, Arnold Mattschull Amtsgericht Münster HRB 8939 Ust.-Id Nr. DE209094382 _______________________________________________ Kea-users mailing list [email protected]<mailto:[email protected]> https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
