Using bind and ad blocking

[Olliver Schinagl]

Hey Mark,

On 05-02-16 22:47, Mark Andrews wrote:
> Read the error message.  It will tell you where a write instance
> is and a read instance is or where two write instances are.  In
> this case it is on lines 7 and 3 of junk.conf (junk.conf:7 and
> junk.conf:3).
>
> 	% cat junk.conf
> 	zone "a" IN {
> 		type master;
> 		file "x";
> 	};
> 	zone "b" {
> 		type slave;
> 		file "x";
> 		masters { 1.1.1.1; };
> 	};
> 	% named-checkconf junk.conf
> 	junk.conf:7: writeable file 'x': already in use: junk.conf:3
> 	%
Oh I know where the dupes are from, it's from the big list of 'ad' 
domains, but they do not have a 'master' entry, they look like your 
example below, but I pretty much solved it using RPZ zone's. Thank you 
for your time however!
> And a example of a shared master file being processed cleanly.
>
> 	% cat shared.conf
> 	zone "a" IN {
> 		type master;
> 		file "x";
> 	};
> 	zone "b" {
> 		type master;
> 		file "x";
> 	};
> 	% named-checkconf shared.conf
> 	%
>
> Mark
>