Named.conf Updates

[rustyautopsy]

I have setup views on my bind box. My views break if I do not comment out the last two line in named.conf...

include "/etc/bind/named.conf.options";
//include "/etc/bind/named.conf.local";
//include "/etc/bind/named.conf.default-zones";

I have my views setup as follows...

//
// Lan zone recursion is the default
//
view "internal-view" {
match-clients { trusted-subnets; };
recursion yes;
include "/etc/bind/named.conf.default-zones";
zone "example.com" {
type master;
file "/etc/bind/db.internal.example.com";
};
zone "1.0.10.in-addr.arpa" {
type master;
notify no;
file "/etc/bind/db.1.0.10.IN-ADDR.ARPA";
};
zone "2.0.10.in-addr.arpa" {
type master;
notify no;
file "/etc/bind/db.2.0.10.IN-ADDR.ARPA";
};
zone "3.0.10.in-addr.arpa" {
type master;
notify no;
file "/etc/bind/db.3.0.10.IN-ADDR.ARPA";
};
};
//
// external zone w/o recursion
//
view "external-view" {
match-clients { any; };
recursion no;
allow-transfer { slaves; };
include "/etc/bind/named.conf.local";
};

What do you suggest is the best way to deal with this? Allowing for the ability to pass is a source attribute into your file resource for /etc/bind/named.conf in config.pp? Managed the resulting named.conf via augeas?

Thanks in advance.

Cheers.

[ajjahn]

Since this module doesn't have any requirements for what is in the named.conf file, and only ensures that it exists. I suppose you could use any method you want to provision the contents of the file. Although, I'd be to adding that functionality if you'd like to take a stab at it.