Re: [DNSOP] Verifying errata 5316 against RFC1034.

2018-04-09 Thread Warren Kumari
On Mon, Apr 2, 2018 at 8:12 PM, Matthew Pounsett wrote: > > > On 2 April 2018 at 09:56, Warren Kumari wrote: >> >> >> This is not clearly a modification to the intended consensus (yet), >> and currently feels unclear to me, so I'm going to give this another >> few days (~1 week) and then, probabl

Re: [DNSOP] Verifying errata 5316 against RFC1034.

2018-04-02 Thread Matthew Pounsett
On 2 April 2018 at 09:56, Warren Kumari wrote: > > This is not clearly a modification to the intended consensus (yet), > and currently feels unclear to me, so I'm going to give this another > few days (~1 week) and then, probably, mark it Hold for Document > Update. I'd still appreciate peoples'

Re: [DNSOP] Verifying errata 5316 against RFC1034.

2018-04-02 Thread Warren Kumari
On Sun, Apr 1, 2018 at 5:06 PM, Evan Hunt wrote: > On Sun, Apr 01, 2018 at 01:33:17PM -0400, Warren Kumari wrote: >> I'm also somewhat confused what the caching the wildcard answer >> *means* - if I have *.example.com cached and then get a query for >> foo.example.com I still need to query for it

Re: [DNSOP] Verifying errata 5316 against RFC1034.

2018-04-02 Thread bert hubert
On Sun, Apr 01, 2018 at 11:58:07PM +0530, Mukund Sivaraman wrote: > Caching takes place not just by BIND, but Unbound as well and does not > cause problems, so the stronger requirement is unnecessary and ought to > be re-worded. PowerDNS recursor will also happily cache a *.record but not do anyth

Re: [DNSOP] Verifying errata 5316 against RFC1034.

2018-04-01 Thread Evan Hunt
On Sun, Apr 01, 2018 at 01:33:17PM -0400, Warren Kumari wrote: > I'm also somewhat confused what the caching the wildcard answer > *means* - if I have *.example.com cached and then get a query for > foo.example.com I still need to query for it (note that this is all > before DNSSEC / Aggressive NSE

Re: [DNSOP] Verifying errata 5316 against RFC1034.

2018-04-01 Thread Mukund Sivaraman
On Sun, Apr 01, 2018 at 01:33:17PM -0400, Warren Kumari wrote: > Can folk help me understand what should happen with this errata? > W To elaborate further: IMO there's no argument against caching if the cached record set (with wildcard owner name) was not used in synthesis of RRs. I suspect RFC 1

[DNSOP] Verifying errata 5316 against RFC1034.

2018-04-01 Thread Warren Kumari
Hi all, We have this errata: https://www.rfc-editor.org/verify_errata_select.php?eid=5316 The document as published says: "A * label appearing in a query name has no special effect, but can be used to test for wildcards in an authoritative zone; such a query is the only way to get a response con