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
Under Ubuntu 16.04 bind9 package uses /etc/bind for its configuration.
named.conf and all of the zone db files are located there.
So I have wasted hours trying to use my existing puppet code using this module that works fine under RHEL 6 & 7, only to discover puppet was writing out to /etc/named.conf but the ubuntu binaries appear to check for /etc/bind/named.conf.
The module defaults to /var/named, which is fine but is RHEL specific.
bind::server::conf doesn't use params in anyway.
The default values for $dump_file, $statistics_file, $memstatistics_file should all be relative to $directory, because even if you overwrite $directory it still tries to write those files out to the preferred /var/named directory.
The text was updated successfully, but these errors were encountered:
Under Ubuntu 16.04 bind9 package uses /etc/bind for its configuration.
named.conf and all of the zone db files are located there.
So I have wasted hours trying to use my existing puppet code using this module that works fine under RHEL 6 & 7, only to discover puppet was writing out to /etc/named.conf but the ubuntu binaries appear to check for /etc/bind/named.conf.
The module defaults to /var/named, which is fine but is RHEL specific.
bind::server::conf doesn't use params in anyway.
The default values for $dump_file, $statistics_file, $memstatistics_file should all be relative to $directory, because even if you overwrite $directory it still tries to write those files out to the preferred /var/named directory.
The text was updated successfully, but these errors were encountered: