Re: Extending UPDATE to add/remove zones
Mark Andrews <[email protected]>
| Newsgroups | gmane.ietf.dnsext |
|---|---|
| Message-ID | <[email protected]> |
In message <[email protected]>, Jay Daley writes : > > On 17/10/2013, at 11:33 AM, Mark Andrews <[email protected]> wrote: > > > Add zone: > > Zone: <zname> <class> NS > > Update: <aname> <ttl> <class> SOA ..... > > <rest of initial zone> > > Additional: > > master TXT [port=3Dvalue] [A=3Dvalue] [AAAA=3Dvalue] = > [key=3Dname[:alg:secret]] [name=3Dname] > > key TXT [key=3Dname[:algorithm:secret]] > > port TXT [port=3Dvalue] > > allow-transfer TXT <TBD> > > allow-query TXT <TBD> > > allow-update TXT <TBD> > > I sympathise with just how easy this would be, especially if the labels = > were prefixed with an underscore to prevent collisions, but I think this = > is a step too far given the variance in implementations and we should = > use NSCP instead. Additional records don't get added to the zone. They supplemental data just like OPT TSIG SIG are supplemental data. That said they could be defined later. > >=20 > > Delete zone: > > Zone: <zname> <class> NS > > Update: <zname> <ttl> ANY SOA > > That's excellent thank you. > > I'll put together a draft. > > Jay > > --=20 > Jay Daley > Chief Executive > .nz Registry Services (New Zealand Domain Name Registry Limited) > desk: +64 4 931 6977 > mobile: +64 21 678840 > linkedin: www.linkedin.com/in/jaydaley > -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ dnsext mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsext