(usagi-users 03509) Re: RCODE =3 (Name Error) + DNS

JINMEI Tatuya / 神明達哉 <[email protected]>
Newsgroups gmane.linux.ipv6.usagi.users
Organization Research & Development Center, Toshiba Corp., Kawasaki, Japan.
Message-ID <y7v4q7v5b0e.wl%[email protected]>
>>>>> On Thu, 6 Oct 2005 10:39:19 +0530, 
>>>>> Sanjib Das <[email protected]> said:

> that i have tested like, i have my own domain "ipv6.domain."
> No within this i have one of my host as "myhost.ipv6.domain."
> but while querying i do it like this

> dig host.ipv6.domain.  AAAA

> getting the response with RCODE = 3. 
> where i got the doubt is like, if we make mistake in the domain name 
> itself
> like, instead of ipv6.domain say i typed ip.domain. In this case also 
> should i get 
> the response with RCODE = 3, if my server is the authritative for this 
> zone 
> (i configured it as root server for my domain).
> In this case i donot get the response with RCODE = 3.

I suspect dig actually asked the real root servers in the Internet.
Make sure that it directly asks your own (internal?) root server which
manages the imaginary "ipv6.domain".

> One thing more, in BIND9, this RCODE = 3 they have represented as NXDOMAIN
> not as Name Error. I donno what this NXDOMAIN really means, whereas it got 
> the
> same RCODE (3) value like Name Error (As per RFC 4074) 

NXDOMAIN is a BIND specific terminology which represents RCODE 3 and
stands for non existent domain.  Since an RFC should be "neutral", it
uses the standard keyword.

BTW: RFC4074 is not a very appropriate reference in this context.  You
might rather want to refer to more basic reference to DNS, such as
RFC1034 and/or RFC1035.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.