In article ,
"Spain, Dr. Jeffry A." wrote:
> Rather than running multiple bind instances on one server, is virtualization
> an option for you? Thus you could build multiple virtual machines each
> running a single bind instance.
Seems like overkill if BIND is the only thing you're running on
>> I need to understand the difference between configuring bind views and
>> having multiple instances of bind. I have 5 network interfaces on my
>> server and I want to have 2 instances of DNS server (just for testing)
>> and I don't know which one to do ?
> BIND views are powerful, but config
> I need to understand the difference between configuring bind views and
> having multiple instances of bind. I have 5 network interfaces on my server
> and I want to have 2 instances of DNS server (just for testing) and I don't
> know which one to do ?
BIND views are powerful, but configuring the
In article ,
Mike Hoskins wrote:
> the other thing is if your testing needs to stop/start named for some
> reason, it might be less impactful to run separate instances. however, if
> you run 'rndc' you will see that many of the commands can be ran in a
> manner that only affects specified views
-Original Message-
From: Amira Othman
Date: Thursday, May 24, 2012 8:04 AM
To:
Subject: different between views and having multiple instances
>Hi all
>
>I need to understand the difference between configuring bind views and
>having multiple instances of bind. I have 5 network interfaces
In theory, you would use views to serve up different data to subnets. For
example, you may want to show your internal clients one set of IP addresses
while the external world see's a subset of that data. That is a perfect
utilization of views.
You may want to setup different instances of BIND
6 matches
Mail list logo
