Re: Extending UPDATE to add/remove zones
Bob Halley <[email protected]>
| Newsgroups | gmane.ietf.dnsext |
|---|---|
| Message-ID | <CE83F61C.79A9%[email protected]> |
On 10/16/13, 7:19, "Dave Lawrence" <[email protected]> wrote: >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. While it would be possible to interpret FQDNs as rooted at some other root it's not a good solution because then there's no way for the data in the update section to refer to something out of the zone. That's OK for owner names, but it's not OK for names in rdata, e.g. the target of a CNAME. Zone templating requires the ability to specify both relative and absolute names, and relative names are not currently representable in the DNS protocol. /Bob _______________________________________________ dnsext mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsext