You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if it's possible with the current architecture of the module, but have there been any discussions around being able to use a non-standard cfg_dir for the named configuration files?
In my home servers, I run named in a chroot environment, which means it actually picks up its configuration files from /var/named/chroot/etc, not from plain /etc. However, at the current time, I don't see any way to get this module to place the named config files anywhere other than the OS-specific default.
The text was updated successfully, but these errors were encountered:
I'm not sure if it's possible with the current architecture of the module, but have there been any discussions around being able to use a non-standard
cfg_dir
for the named configuration files?In my home servers, I run named in a chroot environment, which means it actually picks up its configuration files from
/var/named/chroot/etc
, not from plain/etc
. However, at the current time, I don't see any way to get this module to place the named config files anywhere other than the OS-specific default.The text was updated successfully, but these errors were encountered: