Alan Clegg writes:
If it were me and I had no other choice than to use views, I'd get into
the system and re-wire everything using BIND 9.7.2 and write a set of
scripts that used "rndc addzone" and "rndc delzone" to control the
master and all of the slaves, configure TSIG keys to manage zone
Alan Clegg wrote:
...
Given choices, I think I'm in agreement with you: I'd chose to not do
views.
Based on the posts here, the OP is going to do views. The best thing to
do is provide the best method of replicating those views to the machines
that are providing slave services without using
Alan Clegg wrote:
On 1/1/2011 9:15 AM, Gary Wallis wrote:
You will need to setup one virtual IP for each extra view.
Not since very versions of BIND that are long-since EOL'd. The FAQ goes
into how to use TSIG keys to deal with "picking the right one".
This is what no one here addresses cl
On 1/1/2011 9:15 AM, Gary Wallis wrote:
> You will need to setup one virtual IP for each extra view.
Not since very versions of BIND that are long-since EOL'd. The FAQ goes
into how to use TSIG keys to deal with "picking the right one".
> This is what no one here addresses clearly and upfront:
p...@mail.nsbeta.info wrote:
Two bind servers, one master, one slave.
There are three views at each.
The config is shown below.
But why the first two veiws can get transfered, the third can't be
transfer?
Thanks in advance.
-
master:
You will need to setup one v
Have you looked at the logs?
You may need to change the debug level with rndc. You can also set it
when starting bind - named -d debug-level.
Debug level 5 - "Captures the view being used in order to answer a
request".
Have you verified the two views which are being transferred to make sure
the
Two bind servers, one master, one slave.
There are three views at each.
The config is shown below.
But why the first two veiws can get transfered, the third can't be transfer?
Thanks in advance.
-
master:
options {
directory "/usr/local/named/var/named";
};
7 matches
Mail list logo
