Re. "primary", it is worth noting the definition of the SOA MNAME field in RFC 1035:
MNAME The <domain-name> of the name server that was the original or primary source of data for this zone. I get the impression that sometimes people regard a zone as having one primary or master and all its other servers are secondaries or slaves. But sometimes (eg when configuring slave zones in BIND) you get a per-xfer view of the terminology. Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at > On 2 Apr 2015, at 20:51, Paul Hoffman <paul.hoff...@vpnc.org> wrote: > > Tony. > -- > f.anthony.n.finch <d...@dotat.at> http://dotat.at > > > Primary servers and secondary servers --- These are synonyms for "master > server" and "slave server", > which were the terms used in the early DNS RFCs, and defined below. The > current common usage has > shifted to "primary" and "secondary". > > Slave server --- An authoritative server which uses zone transfer to retrieve > the zone. > (Quoted from {{RFC1996}}, section 2.1) > {{RFC2182}} describes slave servers in detail. > > Master --- Any authoritative server configured to be the source of zone > transfer > for one or more slave servers. (Quoted from {{RFC1996}}, section 2.1) > {{RFC2136}} defines "master" as "an authoritative server configured to be the > source of AXFR or IXFR > data for one or more slave servers". > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
