named.conf.erb assumes named.rfc1912.zones in hardcoded location about puppet-bind

[thias]

This should now be fixed in 1c9dbfc. Also note that RFC1912 and RFC1918 are quite different, and after a quick look, it seems like the Debian file covering RFC1912 and the forward/reverse for loopback addresses and names is /etc/bind/named.conf.default-zones so I have included that one.

But I'm assuming most of you have moved on to better maintained modules anyway (sorry!).

[hybby]

I ran into this issue on Ubuntu 14.04 too.

I had to change the following in thename.conf.erb file to get BIND started...

-include "/etc/named.rfc1912.zones";
+include "/etc/bind/zones.rfc1918";

-    file "named.ca";
+    file "/etc/bind/db.root";

[drequena]

Actually, I didn't even find the rfc1912 and named.ca files on Debian 8.
I had to remove the entries from named.conf.erb in order to have a functional DNS server, and add a "includes" entry so the Debian equivalent file (named.conf.default-zones) could be added.

[rendhalver]

I ran into a similar issue on Ubuntu.
I added named.ca and the rfc1912 zones files in my profile but ran into an issue where apparmor is complaining about the files location.
I am working on a fix that should resolve the issue.

[khaefeli]

added a PR to solve this issue @thias