rndc and views

godfrey peart mgpeart at lgu.ac.uk
Sun Jul 4 23:28:03 UTC 2004


I have setup views on my primary and secondary and it works upto a point.
If I edit external zone data on master and reload , the master sends 
notifiy to slave but
slave doesn't automatically transfer across new data but waits until 
refresh time elapses
then pulls across data. I get round this by connecting to slave and running
rndc reload "myzonedata "  in external
and then slave pulls across  updated zone files, is this correct behaviour ?

------named.conf  on  primary----
acl internal {!172.16.10.24; !172.16.10.23; 127.0.0.1; 172.16/16;};

view internal  {
        match-clients {internal;};
        query-source address 172.16.10.18;
        recursion yes;
zone "myzone.com" in  {
type master;
file "thezone.in";
allow-transfer { key mykey;};
notify-source 172.16.10.18;
};
zone "16.172.in-addr.arpa" in {
type master;
allow-transfer { key mykey;};
notify-source 172.16.10.18;
file "172.16.rev.in";
};
view external  {
match-clients {any;};
recursion no;
query-source address 172.16.10.24;
zone "myzone.com" in {
type master;
file "myzone.ext";
notify-source 172.16.10.24;
};

zone "1.1.10.in-addr.arpa" in{
type master;
file "10.rev.ext";
allow-transfer { key mykey;};
notify-source 172.16.10.24;
};

---------named.conf  sec---------

acl internal {!172.16.10.24; !172.16.10.23; 127.0.0.1; 172.16/16;};

view internal {
        match-clients {internal;};
        recursion yes;
zone "myzone.com" in  {
type slave;
masters {172.16.10.18;};
file "thezone.in";
transfer-source 172.16.10.19;
allow-transfer { key mykey;};
};
zone "16.172.in-addr.arpa" in {
type slave;
masters {172.16.10.18;};
transfer-source 172.16.10.19;
allow-transfer { key mykey;};
file "172.16.rev";
};

view external  {
match-clients {any;};
recursion no;
query-source address 172.16.10.23;
zone "myzone.com" in {
type slave;
masters {172.16.10.18;};
transfer-source 172.16.10.23;
allow-transfer { key mykey;};
file "thezone.ext";
};

zone "1.1.10.in-addr.arpa" in{
type slave;
masters {172.16.10.18;};
transfer-source 172.16.10.23;
file "10.rev.ext";
allow-transfer { key mykey;};
};







More information about the bind-users mailing list