General discussion

Locked

Nslookup -Debug returns a rcode = NXDO

By jward ·
This is an extention to my previous question "Some DHCP Clients don't get FQDN"
below is the response I get from
nslookup -debug

> wardjlap
Server: geisel.mydomain.com
Address: 172.22.0.33

------------
Got answer:
HEADER:opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0

QUESTIONS:
wardjlap.mydomain.com,type = A, class = IN

------------
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
*** Request to geisel.mydomain.com timed-out

Clients are configured to use DHCP and DHCP is configured to use WINS with NodeType = 0x8

In the example above nslookup returns an error code "rcode = NXDOMAIN" and the request
timed-out.

All client are on the same domain and subnet and configured to use DHCP yet some clients names are added to WINS and some are not?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Nslookup -Debug returns a rcode = NXDO

by pete.zerger In reply to Nslookup -Debug returns a ...

The answer to your problem I believe is in this Technet Article

http://support.microsoft.com/support/kb/articles/Q186/8/20.ASP

They save basically when WINS lookup is enabled in your DNS settings the error occurs when WINS returns 'name not found'.
So maybe trying removing the checkmark by 'Use WINS for DNS resolution' and that could help.

Your WINS issue is a separate problem and I would need more info to figure out why names aren't showing. If you have more info, emial me at pete.zerger@jumpfaster.com

Collapse -

Nslookup -Debug returns a rcode = NXDO

by jward In reply to Nslookup -Debug returns a ...

The question was auto-closed by TechRepublic

Collapse -

Nslookup -Debug returns a rcode = NXDO

by simon.wellborne In reply to Nslookup -Debug returns a ...

Further to the email, are you sure you have an A record in your zone for the DNS servers?

Without, you will get NXDOMAIN errors.

The Technet article that was referred to by the previous correspondent I think relates to rcode=3 errors, Name Error - Meaningful only for responses from an authoritative name server, this code signifies that the domain name referenced in the query does not exist.

I think you are getting rcode=2 errors, NS not found (based on the timeout errors etc).

Collapse -

Nslookup -Debug returns a rcode = NXDO

by jward In reply to Nslookup -Debug returns a ...

The question was auto-closed by TechRepublic

Collapse -

Nslookup -Debug returns a rcode = NXDO

by jward In reply to Nslookup -Debug returns a ...

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Operating Systems Forums