>> Secondly: can someone please explain to me why the idea of a
>> "primary master" where the zone data originates from and where
>> updates are performed is considered archaic?
>
> I think the only in-protocol use of the MNAME field is to
> specify the name to which UPDATE messages are sent.
Really? I read the NOTIFY RFC (1996) so that if the MNAME name
server is included in the NS set, it will by default be excluded
from receiving NOTIFY messages from the other name servers when
they reload the zone, ref. the definition of "Notify set" in RFC
1996. Unsurprisingly, BIND has code to do this:
result = dns_name_dup(&soa.origin, zone->mctx, &master);
...
/*
* Process NS RRset to generate notifies.
*/
...
/*
* Don't notify the master server unless explicitly
* configured to do so.
*/
if (!DNS_ZONE_OPTION(zone, DNS_ZONEOPT_NOTIFYTOSOA) &&
dns_name_compare(&master, &ns.name) == 0) {
result = dns_rdataset_next(&nsrdset);
continue;
}
Regards,
- Håvard
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
