Hi! The linux kernel has a feature called "inotify". It basically lets you put a "listener" on any file on the system and run a script when that file changes.
You could use that feature to listen to the named.conf file and run a script that replicates the the clones whenever it has been changed. To get you started, take a look at this tool: https://github.com/rvoicilas/inotify-tools/wiki Other ways would be to configure bind to work in replication mode. Regards, Daniele On Friday, June 26, 2015 at 2:50:32 AM UTC+8, [email protected] wrote: > > I know that scalr can do DNS, and propagate new records immediately after > a node comes up. I really like this functionality. > > However, i do not want my scalr host acting as the primary DNS server for > my org. I'd like to set up a few DNS slaves that replicate from scalr. > > I know that changes will be made in named.conf file, but i guess that my > question is what, if anything, do i need to do on the scalr host to make > sure that the zone files scalr generates are cloned? > > > Thanks for your time! > > -Karl > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
