| fantasygoat |
04-12-2011 03:06 PM |
bind Views with Master and Slave
I have bind configured with Internal and External views, but the slave server is transferring only the Internal zone files for both Internal and External - a diff shows no difference, and the log shows the same serial number:
Quote:
12-Apr-2011 15:56:55.016 general: zone example.com/IN/INTERNAL: Transfer started.
12-Apr-2011 15:56:55.017 xfer-in: transfer of 'example.com/IN' from 172.16.0.10#53: connected using 172.16.0.11#43425
12-Apr-2011 15:56:55.025 general: zone example.com/IN/INTERNAL: transferred serial 2011022206
12-Apr-2011 15:56:55.027 xfer-in: transfer of 'example.com/IN' from 172.16.0.10#53: end of transfer
12-Apr-2011 15:56:55.517 general: zone example.com/IN/EXTERNAL: Transfer started.
12-Apr-2011 15:56:55.518 xfer-in: transfer of 'example.com/IN' from 172.16.0.10#53: connected using 172.16.0.11#59096
12-Apr-2011 15:56:55.527 general: zone example.com/IN/EXTERNAL: transferred serial 2011022206
12-Apr-2011 15:56:55.527 xfer-in: transfer of 'example.com/IN' from 172.16.0.10#53: end of transfer
|
Here's the config on the master:
Quote:
options {
listen-on-v6 { none; };
pid-file "/var/run/named/named.pid";
directory "/var/named";
allow-transfer { 172.16.0.0/12; };
notify explicit;
version none;
hostname none;
server-id none;
max-ncache-ttl 3;
recursive-clients 10000;
};
view INTERNAL {
match-clients { 172.16.0.0/12; 192.168.0.0/16; 127.0.0.1; };
recursion yes;
also-notify { 172.16.0.11; };
zone "." IN {
type hint;
file "named.root";
};
# Forward zones
zone "example.com" {
type master;
file "internal/example.com.zone";
};
# Reverse zones
zone "0.16.172.in-addr.arpa" {
type master;
file "internal/172.16.0.rev";
};
};
view EXTERNAL {
match-clients { any; };
recursion no;
also-notify { 172.16.0.11; };
zone "example.com" {
type master;
file "external/example.com.zone";
};
};
logging {
channel logfile {
file "/var/log/named.log" versions 3 size 1m;
print-time yes;
print-category yes;
};
category default {logfile;};
category lame-servers { null; };
category notify { logfile; };
};
include "/etc/rndc.key";
|
And the slave config:
Quote:
options {
listen-on-v6 { none; };
pid-file "/var/run/named/named.pid";
directory "/var/named";
allow-transfer { 172.16.0.0/12; };
notify explicit;
version none;
hostname none;
server-id none;
max-ncache-ttl 3;
recursive-clients 10000;
};
view INTERNAL {
match-clients { 172.16.0.0/12; 192.168.0.0/16; 127.0.0.1; };
recursion yes;
zone "." IN {
type hint;
file "named.root";
};
# Forward zones
zone "example.com" {
type slave;
file "internal/example.com.zone";
masters { 172.16.0.10; };
};
# Reverse zones
zone "0.16.172.in-addr.arpa" {
type slave;
file "internal/172.16.0.rev";
masters { 172.16.0.10; };
};
};
view EXTERNAL {
match-clients { any; };
recursion no;
zone "example.com" {
type slave;
file "external/example.com.zone";
masters { 172.16.0.10; };
};
};
logging {
channel logfile {
file "/var/log/named.log" versions 3 size 1m;
print-time yes;
print-category yes;
};
category default {logfile;};
category lame-servers { null; };
category notify { logfile; };
};
include "/etc/rndc.key";
|
What am I missing in the config so the slave server properly receives updates from the master for both views? |
