In message <1401424053.51486.yahoomail...@web121604.mail.ne1.yahoo.com>, Jiann-
Ming Su writes:
>
>
> Looking through the traces of the NXDomain vs NoError responses. The
> NoError response includes the list of the Internet root servers. This
> would definitely be a valid response for a "." quer
Looking through the traces of the NXDomain vs NoError responses. The NoError
response includes the list of the Internet root servers. This would definitely
be a valid response for a "." query. I wonder if I've run into a bug with this
particular version of BIND where it ignores or changes t
> On Thursday, May 29, 2014 6:53 PM, Jiann-Ming Su wrote:
> >
>
>
>
>
>
>> On Thursday, May 29, 2014 6:32 PM, Mark Andrews
> wrote:
>> >
>> In message <53879683.2080...@chrysler.com>, Kevin Darcy writes:
>>> Why the different RCODES? See RFC 2308. Short version: the
>> "NODATA"
> On Thursday, May 29, 2014 6:32 PM, Mark Andrews wrote:
> >
> In message <53879683.2080...@chrysler.com>, Kevin Darcy writes:
>> Why the different RCODES? See RFC 2308. Short version: the
> "NODATA"
>> response occurs when the QNAME exists, but no records match QTYPE. It
>> will also
In message <53879683.2080...@chrysler.com>, Kevin Darcy writes:
> Why the different RCODES? See RFC 2308. Short version: the "NODATA"
> response occurs when the QNAME exists, but no records match QTYPE. It
> will also occur if the QNAME is merely a "branch" to something further
> down in the hi
Why the different RCODES? See RFC 2308. Short version: the "NODATA"
response occurs when the QNAME exists, but no records match QTYPE. It
will also occur if the QNAME is merely a "branch" to something further
down in the hierarchy (a so-called "empty non-terminal"), and owns no
records of its o
Hi Jiann-Ming,
Hopefully someone else didn't beat me to the reply.
"No such name" is an NXDOMAIN response. It occurs when there are no
records for a given name. For example, if you query
fasdf---sadfasdfasdf.com
(I hope this doesn't actually exist ;-)
you'll get a "No such na
What could cause BIND to respond with reply code 0x8083 (no such name) vs
0x8080 (no error)?
I have an app doing srv queries without the domain name appended. One time,
server will respond with no such name (flags 0x8083) which causes the app to
query again with domain name appended. Another
8 matches
Mail list logo
