In message , Tony F
inch writes:
> Paul Vixie 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
Paul Vixie 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 SOA. minima
On Wed, Apr 1, 2015 at 4:53 PM, Paul Vixie wrote:
>
>
> 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 r
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. S
On Wed, Apr 1, 2015 at 4:37 PM, 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
>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'
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 cachin
On Apr 1, 2015, at 11:24 AM, 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.
>
> > 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
Sorry for the belated reply.
On Mar 24, 2015, at 1:03 PM, Shumon Huque 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
> >empty. Tha
Shumon Huque 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 in RFC 40
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
12 matches
Mail list logo
