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 : > And what would your solution be to signifying that a zone is to be > deleted? Without one we have to abandon extending UPDATE and burn an > opcode. > > Jay Add zone: Zone: <zname> <class> NS Update: <aname> <ttl> <class> SOA ..... <rest of initial zone> Additional: master TXT [port=value] [A=value] [AAAA=value] [key=name[:alg:secret]] [name=name] key TXT [key=name[:algorithm:secret]] port TXT [port=value] allow-transfer TXT <TBD> allow-query TXT <TBD> allow-update TXT <TBD> Delete zone: Zone: <zname> <class> NS Update: <aname> <ttl> ANY SOA The use of type NS in the zone section indicates that this is a whole of zone operation. Mark > -- > 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