primary/secondary configuration

[Barbara Nowak]

Hi,


Barry Margolin <barmar at alum.mit.edu> wrote:


[...]

> I'm going to assume .1 is the master and .100 is the slave.  The master 
> nameserver needs a second IP configured on it, let's say 192.168.0.2.

> In the public view, the slave should pull the zone from 192.168.0.1, in 
> the private view it should pull from 192.168.0.2.
Ah yes... I've tested above yesterday and it is work no correctly..


> match-destination { 192.168.0.1; };
> notify-source { 192.168.0.1; };

> and the private view should contain:

> match-destination { 192.168.0.2; };
> notify-source { 192.168.0.2; };
It has been helpful
Thanks for help.

-- 
Barbara