thanks for the reply chris, My only question about using views is how are my dns server respond on the IP's that i designated them? is there a listen-address where i can bind the ip to that specific view? I have 2 boxes but i want to run 3 different bind servers on each.
Box#1 dns1.domain1.com dns1.domain2.com dns1.domain3.com Box#2 dns2.domain1.com dns2.domain2.com dns2.domain3.com Each of them have their own dedicated IP. sorry for the newbie questions, I'm still reading up on the bind view material its still new to me. Any help will be greatly appreciated -b On Thu, Sep 18, 2008 at 11:40 AM, Chris Buxton <[EMAIL PROTECTED]> wrote: > It's better (simpler) to use views. You get almost exactly the same effect, > without for example having to manage multiple rndc channels. (By default, > there is a sole control channel at 127.0.0.1:953, and maybe also at ::1.953; > with multiple instances of named running, you have to override that for one > or both instances.) > > With views, each view has its own authoritative zones, its own cache and > resolver configuration (e.g. forward & stub zones, root hints, etc.), and > optionally its own ACL's, keys, servers, and so forth. Each view is almost a > separate instance of named. > > Chris Buxton > Professional Services > Men & Mice > > On Sep 18, 2008, at 10:29 AM, Beavis wrote: > >> Greetings all, >> >> I want to get some input about running multiple instances of bind >> on a dns box. I'm planning to running different instance of named and >> bind them to different IP's I have in one single box. will this be a >> recommended course of action? or would it be better to run it through >> bind views? >> >> >> any input will be awesomely appreciated. >> >> regards, >> -b >> > >
