Re: Extending UPDATE to add/remove zones
Dave Lawrence <[email protected]>
| Newsgroups | gmane.ietf.dnsext |
|---|---|
| Message-ID | <[email protected]> |
Andreas Gustafsson writes: > > None of these records may be fully qualified so as to ensure that > > they apply to all the zones listed. > > There is no way to encode that in the DNS protocol. All names are > fully qualified on the wire; relative names are merely a convenience > notation used in master files and other user interfaces. Well sure there is, you declare "in this special type of message, all of the records in the update section are relative to the zones in the zone section." I inferred the original intent was to be able to add a block of zones all with the same template. Personally I think that's a bad idea, or at the least underspecified in the original description -- does this concept apply only to owner names, or names within rdata as well? It seems like a premature optimization though, and puts too many eggs in one basket. Just using separate messages for each zone with everything fully-qualified does not seem like onerous overhead to me. _______________________________________________ dnsext mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsext