> Colm MacCárthaigh <mailto:c...@allcosts.net> > Wednesday, January 21, 2015 6:52 AM > > > RRSet: Are the RRs in an RRSet required to have different data? For > types such as A/AAAA/SRV/MX this makes sense, but maybe not for TXT. I > also think views and other implementation specific features confuse > things here. A user might have 10 A records defined for a given name; > but if their DNS server returns one at a time (say it's using weighted > round robin) - I don't think of the 10 as an RRSet; but rather it's 10 > RRSets. What's actually sent on the wire is what matters, I think.
if their server returns only one RR at a time, then there are ten RRsets, as you say. however, such a server would not be speaking the DNS protocol as defined, if it starts from a zone file or zone transfer where there is within the zone ten RR's for a given name. so, by definition, the current text is correct. > > Stealth server: this definition seems a bit contradictory. Starts out > by saying it's a slave, but then says it can also be a master. in <http://www.rfc-editor.org/rfc/rfc1996.txt> we see: 1.3. This document intentionally gives more definition to the roles of "Master," "Slave" and "Stealth" servers, their enumeration in NS RRs, and the SOA MNAME field. In that sense, this document can be considered an addendum to [RFC1035]. ... 2.1. The following definitions are used in this document: Slave an authoritative server which uses zone transfer to retrieve the zone. All slave servers are named in the NS RRs for the zone. Master any authoritative server configured to be the source of zone transfer for one or more slave servers. Primary Master master server at the root of the zone transfer dependency graph. The primary master is named in the zone's SOA MNAME field and optionally by an NS RR. There is by definition only one primary master server per zone. Stealth like a slave server except not listed in an NS RR for the zone. A stealth server, unless explicitly configured to do otherwise, will set the AA bit in responses and be capable of acting as a master. A stealth server will only be known by other servers if they are given static configuration data indicating its existence. Notify Set set of servers to be notified of changes to some zone. Default is all servers named in the NS RRset, except for any server also named in the SOA MNAME. Some implementations will permit the name server administrator to override this set or add elements to it (such as, for example, stealth servers). 2.2. The zone's servers must be organized into a dependency graph such that there is a primary master, and all other servers must use AXFR or IXFR either from the primary master or from some slave which is also a master. No loops are permitted in the AXFR dependency graph. in other words, what makes you a master is that someone is transferring from you. the primary master is the only master that by definition cannot also be a slave. the terms "master" and "slave" refer to protocol roles within the AXFR/IXFR transaction. -- Paul Vixie
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
