On 29 September 2016 at 15:07, Tim Daneliuk <tun...@tundraware.com> wrote:
> > > No, not really. It's for a private cloud microservices system we're > thinking through. We already run most/many of the various service > backends in user space so that the app devs and support folks can control > their own universe without having to constantly invoke someone with sudo > or root or firecall permissions. Because of very strict audit and > regulatory constraints, there is zero chance they'll ever get root/sudo > access to the DNS config, so running our private DNS just for this > subset of private client/cloud users may make sense. > > I suppose you could leave yourself an unprivileged config file... have them put you in group 'dns' or something, and make all the configs and zone files writable by that group. At least that way all you need your sysadmins for is to issue the 'rndc reconfig' command.
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
