On Wed, Jan 21, 2015 at 7:25 AM, Paul Vixie <p...@redbarn.org> wrote: > > 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. >
If there are two zones for the same name, with different views, do the RRs of a given name and type in both zones form a single rrset? I don't think so. Zone files aren't a requirement of the DNS protocol either; and I don't think there's any case to be made that the configuration of multiple rrsets for the same name/type is not speaking the DNS protocol as defined. > 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 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. > > It might be worth updating the text to say "is often also a master" to make the non-exclusivity between master and slave a bit more clear. -- Colm
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
