Hi,
I would like to ask whether *a slave* for a zone "example.com", say
10.10.10.5 (whose master - and the zone's primary master - is e.g.
10.10.10.2), can be configured *at the same time* as master for the
same zone (example.com) with other slaves (e.g. 10.10.10.10 &
10.10.10.11) which would be configured as slaves of 10.10.10.5 (slaves
of a slave), provided that the backend supports master/slave functions.
Is "also-notify" supported? (I see in the documentation release notes
that "/Infrastructure for 'also-notify' statements added/", but does
"also-notify" behave as in BIND9?)
For example, for the BIND backend, is it supported to have in named.conf
of 10.10.10.5:
zone "example.com" {
type slave;
file "db.example.com";
masters { 10.10.10.2 };
notify yes;
also-notify { 10.10.10.10; 10.10.10.11; };
};
In BIND9, with this configuration, the 10.10.10.5 slave would receive
(NOTIFY - if supported by 10.10.10.2 backend - and) AXFRs from
10.10.10.1 but it would also send NOTIFY messages to 10.10.10.10 and
10.10.10.11 which are configured to have 10.10.10.5 as a master, and it
would also send AXFRs to them, even if they are not included in the
zone's NS records (if the are, also-notify would not be needed). With
this setup, would pdns on 10.10.10.5 send such NOTIFY messages (and,
subsequently, AXFRs) to 10.10.10.10 and 10.10.10.11 ?
Thanks,
Nick
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
