Re: [DNSOP] ANAME precedence [issue #58]

2019-04-30 Thread Matthijs Mekking
Hi, Jan and everyone else, thanks for your feedback. It feels indeed like we should continue with the behavior that ANAME will take precedence over A and when on the same name. I shall go over the draft and see if the text is correct in that sense. Best regards, Matthijs On 4/30/19 11:56

Re: [DNSOP] ANAME precedence [issue #58]

2019-04-30 Thread Jan Včelák
On Fri, Apr 26, 2019 at 8:30 PM 神明達哉 wrote: > > Jan Včelák mentioned that at least NS1 uses a different order of > > priority: If an sibling address record exists next to the ANAME it takes > > precedence and no target lookup is done for that address record type. > > if there's a specific use case

Re: [DNSOP] ANAME precedence [issue #58]

2019-04-26 Thread 神明達哉
At Fri, 26 Apr 2019 09:16:58 +0200, Matthijs Mekking wrote: > > Also, especially if both and A sibling records are available, > > what's the purpose of ANAME in the first place if it's (effectively) > > not used? > > > > I'm sure I'm just confused and don't understand the expected usage, > >

Re: [DNSOP] ANAME precedence [issue #58]

2019-04-26 Thread Matthijs Mekking
On 4/25/19 8:34 PM, 神明達哉 wrote: > At Wed, 24 Apr 2019 11:44:37 +0200, > Matthijs Mekking > wrote: > >> I would like to start separate threads on the remaining issues of the >> ANAME draft. One issue that remains to be solved is whether having an A >> or record

Re: [DNSOP] ANAME precedence [issue #58]

2019-04-25 Thread Anthony Eden
I've commented on the GH issue directly. -Anthony P.S. To everyone involved, thank you for continuing your hard work on this specification. On Wed, Apr 24, 2019 at 5:45 AM Matthijs Mekking wrote: > Hi, > > I would like to start separate threads on the remaining issues of the > ANAME draft. One

Re: [DNSOP] ANAME precedence [issue #58]

2019-04-25 Thread 神明達哉
At Wed, 24 Apr 2019 11:44:37 +0200, Matthijs Mekking wrote: > I would like to start separate threads on the remaining issues of the > ANAME draft. One issue that remains to be solved is whether having an A > or record next to the ANAME should take precedence or not. > > Draft: https://data

[DNSOP] ANAME precedence [issue #58]

2019-04-24 Thread Matthijs Mekking
Hi, I would like to start separate threads on the remaining issues of the ANAME draft. One issue that remains to be solved is whether having an A or record next to the ANAME should take precedence or not. Draft: https://datatracker.ietf.org/doc/draft-ietf-dnsop-aname/ Issue: https://gith