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 9:47 AM, Mark Andrews <[email protected]> wrote:
>
> >
> > In message <[email protected]>, Jay
> Daley writes
> > :
> >> Thanks to all those that replied.  I've summarised and responded to
> the point
> >> s below:
> >>
> >>
> >> 1.  The restriction on FQDNs is too complex and there's no problem
> with provi
> >> sioning multiple zones in multiple packets.
> >>
> >> I agree and I'll change it so that only one master can be added per
> update.
> >> I was indeed thinking about zone templating and that's not a DNS
> issue.
> >>
> >>
> >> 2.  Clarify what the ZCLASS needs to be set to.
> >>
> >> ZCLASS == ANY means delete,  ZCLASS != ANY means add.
> >
> > If you have example.net/in and example.net/hs which example.net are you
> > referring to with example.net/any?
>
> We've already got that problem:
>
> In UPDATE as it currently exists if you have two different RRs  of the
> same type and different class in the same zone then which is being
> referred to with CLASS == ANY ?

A zone, by definition, only contains records of a single class.  The zone
section specify the class of the zone being operated on.

Zone:  example.net IN SOA
Update: example.net ANY TXT

Says delete all example.net IN TXT records.

> Jay
>
> >
> > Mark
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: [email protected]
>
>
> --
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.