Automatic refresh secondary when primary change
Jeff Reasoner
jeff.reasoner at mail.hccanet.org
Thu Feb 2 16:20:20 UTC 2006
First off, if you have 2 views you only need 1 acl. Secondly, you need
to make sure that the 2 IP addresses on your server do not both match
that acl.
if you have
acl internal {192.168.0/24; };
your master could be 192.168.0.1/24 and 172.16.1.2/24
only the first address matches the view:
view "internal-in" {
match-clients {internal; };
notify yes;
zones in that view look like:
zone "domain.com"{
type master;
file "db.internal.domain.com";
allow-transfer {192.168.0.2; };
};
and the other view:
view "any" {
match-clients { any; };
notify yes;
zone "domain.com"{
type master;
file "db.domain.com";
allow-transfer {192.168.0.2; 172.16.1.2; };
also-notify {172.16.1.2; };
};
In named.conf on the secondary, use the same acl and views, just change
the zone info:
zone "domain.com"{
type slave;
file "db.internal.domain.com";
masters {192.168.1.1; };
};
zone "domain.com"{
type slave;
file "db.domain.com";
masters {172.16.1.1; };
};
On Thu, 2006-02-02 at 08:56, Sim wrote:
> > And ip-secondary only mentioned the private IPs and not the external IPs.
> > But if you have correct NS information then you won't need allow-notify at
> > all.
>
> Hi to All!
>
> I have only one public IP over Primary and one public IP over Secondary
>
> In this way I have "internal-in" for my public range (subnet) and
> "external-in" for "any".
>
> I have read the FAQ and see this ANSWER:
>
> ""You will need to give the master and slave multiple IP addresses and
> use those to make sure you reach the correct view on the other
> machine.""
>
> Now, is it correct use this solution or I need to remove "internal-in"
> from two server, and use only "external-in" ?
>
> Thanks
>
>
More information about the bind-users
mailing list