Joe Abley wrote:
> STD 13 assumes a model where there is a single authoritative nameserver which
> acts as a source of truth for zone data ("primary"), from which other
> nameservers retrieve data and also make it available ("secondary"). As such
> they describe the whole of a simple directed graph of zone transfers.
>
> In my experience, in common usage today, master and slave describe functions
> along a single edge of such a graph. A single piece of software might act as
> a master server on one edge, and a slave on another. As such those terms can
> be used to describe more complicated graphs than the particular topology
> imagined in STD 13.
It's not the case that you can only build simple directed graph XFR
topologies using the STD 13 model. RFC 1034 describes an "intermediate
secondary" which seems to be exactly what you described, a server that
performs both XFR-in and XFR-out.
Each secondary server is required to perform the following operations
against the master, but may also optionally perform these operations
against other secondary servers. This strategy can improve the transfer
process when the primary is unavailable due to host downtime or network
problems, or when a secondary server has better network access to an
"intermediate" secondary than to the primary.
--
Robert Edmonds
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
