Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Mark Andrews
In message alpine.lsu.2.00.1504012227030.13...@hermes-1.csi.cam.ac.uk, Tony F inch writes: Paul Vixie p...@redbarn.org wrote: John Levine wrote: A very short survey reveals that unbound and 8.8.8.8 return SOA, bind doesn't. So it's not all the time, but it's pretty common. in

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Paul Hoffman
On Apr 1, 2015, at 11:24 AM, Evan Hunt e...@isc.org wrote: Should we also mention that NODATA responses usually include a SOA record in the authority section to indicate to resolvers how long to do negative caching for? That does not seem to be established firmly enough for us to add.

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Paul Hoffman
Sorry for the belated reply. On Mar 24, 2015, at 1:03 PM, Shumon Huque shu...@gmail.com wrote: Some comments on draft-hoffman-dns-terminology NODATA -- This is not an actual response code, but instead is the combination of an RCODE of 0 (NOERROR) and an Answer section that is

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Evan Hunt
Should we also mention that NODATA responses usually include a SOA record in the authority section to indicate to resolvers how long to do negative caching for? That does not seem to be established firmly enough for us to add. It's necessary for negative caching, so I believe it's

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Paul Vixie
Evan Hunt wrote: Should we also mention that NODATA responses usually include a SOA record in the authority section to indicate to resolvers how long to do negative caching for? That does not seem to be established firmly enough for us to add. It's necessary for negative caching, so I

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Tony Finch
Paul Vixie p...@redbarn.org wrote: John Levine wrote: A very short survey reveals that unbound and 8.8.8.8 return SOA, bind doesn't. So it's not all the time, but it's pretty common. in BIND it's an option. It is? I can't work out how to make it produce a negative response without a

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread John Levine
Good point, I was only thinking of recursive answers, and I don't think I see SOAs there all the time. We can add that NODATA responses for authoritative responses include the SOA. A very short survey reveals that unbound and 8.8.8.8 return SOA, bind doesn't. So it's not all the time, but it's

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Shumon Huque
On Wed, Apr 1, 2015 at 4:37 PM, John Levine jo...@taugh.com wrote: Good point, I was only thinking of recursive answers, and I don't think I see SOAs there all the time. We can add that NODATA responses for authoritative responses include the SOA. A very short survey reveals that unbound and

Re: [DNSOP] comments on DNS terminology draft

2015-04-01 Thread Paul Vixie
John Levine wrote: Good point, I was only thinking of recursive answers, and I don't think I see SOAs there all the time. We can add that NODATA responses for authoritative responses include the SOA. A very short survey reveals that unbound and 8.8.8.8 return SOA, bind doesn't. So it's

Re: [DNSOP] comments on DNS terminology draft

2015-03-25 Thread Tony Finch
Shumon Huque shu...@gmail.com wrote: Apex -- The SOA and NS RRsets at the origin of a zone. This is also called the zone apex. Why is it only the SOA and NS RRsets? I would suggest defining it in terms of the domain name. Yes. Paul likes to quote existing RFCs, so, the definition

[DNSOP] comments on DNS terminology draft

2015-03-24 Thread Shumon Huque
Some comments on draft-hoffman-dns-terminology NODATA -- This is not an actual response code, but instead is the combination of an RCODE of 0 (NOERROR) and an Answer section that is empty. That is, it indicates that the response is no answer, but that there was not supposed to be