zone files with dynamic records #114
-
|
I scoured the documentation, but I don't see anywhere noted how to tell maradns that a zone file has changed. I assume the only way is to completely restart maradns, but I'm wondering if there is another way (eg send a HUP, rebuild some database, etc...) that might be faster and more atomic. The reason I'm asking is I have some records in my zone that are dynamic. I would have an external process rewrite the zone file and then do what? Restart maradns? I know I could figure this out by experimenting and reading the code, but this seems like something that should be explained in either the zone file man page or the maradns man page. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Well, the answer, in fact, is in the documentation, but not in the man page, FAQ, or other obvious place: https://github.com/samboy/MaraDNS/blob/master/doc/en/text/dnsslave.txt Note also that maradns must be restarted to reload the updated zone files. I should probably add a note to the maradns or mararc man page. (Reloadable zone files would probably require using a b-tree instead of a hash for the internal representation of records; the advantage of a single hash is that it’s faster) |
Beta Was this translation helpful? Give feedback.
-
|
I have updated MaraDNS’s documentation to note this in the maradns and mararc man pages. For people who wish this functionality, NSD or KnotDNS might (or might not, I haven’t checked) work out for you: |
Beta Was this translation helpful? Give feedback.
-
|
Locking discussion to stop spam bots. |
Beta Was this translation helpful? Give feedback.
Well, the answer, in fact, is in the documentation, but not in the man page, FAQ, or other obvious place: https://github.com/samboy/MaraDNS/blob/master/doc/en/text/dnsslave.txt
Note also that maradns must be restarted to reload the updated zone files.
I should probably add a note to the maradns or mararc man page.
(Reloadable zone files would probably require using a b-tree instead of a hash for the internal representation of records; the advantage of a single hash is that it’s faster)