constructing named.conf

[Chris Buxton]

No, there is no functional difference. Yes, this is what you want to do.

If you want all zones in a view to have the same allow-transfer list  
and also-notify list, then it makes sense to put those statements  
into your view statement, rather than inside each and every zone  
statement.

Chris Buxton
Men & Mice
Take control of your network

On Sep 9, 2006, at 6:31 AM, Jonathan Horne wrote:

> is there any functional difference between:
>
> view "internal" {
>         match-clients { !192.168.1.49; mynets; };
>         recursion yes;
>         zone "mynet.com" {
>                 type master;
>                 file "/etc/namedb/master/mynet.com.i.hosts";
>                 allow-transfer { any; };
>                 also-notify { 192.168.1.50; };
>                 notify yes;
>                 };
>
>
> and:
> view "internal" {
>         match-clients { !192.168.1.49; mynets; };
>         recursion yes;
> 	allow-transfer { any; };
>         also-notify { 192.168.1.50; };
>         notify yes;
> 	zone "mynet.com" {
>                 type master;
>                 file "/etc/namedb/master/mynet.com.i.hosts";
>                 };
>
>
> it would seem,that the second example would be the more efficient  
> way to go,
> that i would not have to add the transfer/notify commands to each  
> of my
> zones?  am i on the right page here?  right now my named.conf has the
> transfer and notify under each zone, and i would like to clean it  
> up, if this
> would be a proper thing to do.  (under the assumption that i want  
> every zone
> in the internal view to follow the same behaviors, etc etc).
>
> thanks,
> jonathan
>
>
>