Re: DynDB - handling arbitrary zones

2019-04-01 Thread Tony Finch
Klaus Malorny wrote: > > The main problem is that I don't know which zones I will have to serve > beforehand, and they may be many and may change over time, i.e. simply the > typical pattern of an ISP. I want to avoid to dynamically create the > configuration file and trigger the reloading

Re: DynDB - handling arbitrary zones

2019-04-01 Thread Petr Mensik
Sounds like something RPZ might able to do on the first glance. Note there is also rndc addzone method, which may allow runtime reconfiguration of some sort without generation of config files. May or may be not what you need. Might be handy for simple empty zones. Expect some assumptions, dyndb

Re: DynDB - handling arbitrary zones

2019-04-01 Thread Klaus Malorny
On 01.04.19 11:18, Petr Mensik wrote: Hi Klaus, [...] Thanks for the response. I have seen the LDAP implementation, but haven't looked deeper into it. Maybe I will. The main problem is that I don't know which zones I will have to serve beforehand, and they may be many and may change

Re: DynDB - handling arbitrary zones

2019-04-01 Thread Petr Mensik
Hi Klaus, I would recommend taking a look at bind-dyndb-ldap documentation [1], as I think it still is the only one plugin in active use. Unfortunately not under active development, but should be able to answer many of your questions. Some questions could be asked in FreeIPA mailing list, but it