All zone blocks for "public" view should be listed here in "internal"too!

Kevin Darcy kcd at
Fri Sep 24 14:19:24 UTC 2010

If you want that level of separation, why not go even further and have a 
separate instance of named running on a separate address? I assume you 
have a way to selectively tell clients to use a different address for 
DNS resolution, either through DHCP, /etc/resolv.conf or interactively 
via the command line.

That way, your "proposed" config can look as close as possible to the 
"running" config -- no "view" complications -- and maybe the only thing 
you have to change when you promote-to-production is the contents of 
"listen-on" (maybe the directory too, although if both instances are 
chroot'ed even that might not be necessary).

                                 - Kevin

On 9/23/2010 4:13 PM, Bèrto ëd Sèra wrote:
>     Hi!
>     why do you use views then? I guess there's no need for it...
> Because I usually tend to modify a proposed configuration as little as 
> possible, as long as it doesn't cause trouble. But it looks like this 
> one is quite far from what a web-server needs.
> Bèrto
> _______________________________________________
> bind-users mailing list
> bind-users at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list