Re: Forwarders cannot be validated and recursive query fails
- From: "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname@xxxxxxxxxxx>
- Date: Tue, 24 Feb 2009 03:24:30 -0500
In news:4BDEE339-ED75-4D9E-B08B-78A444CD8474@xxxxxxxxxxxxx,
Bennett <Bennett@xxxxxxxxxxxxxxxxxxxxxxxxx>, posted the following:
Never considered the TCP/UDP aspect of telnet. Have to remember that.
:)
Already used nslookup d2 to test & failed (hadn't tried set vc, but
that failed, too). I had even compared d2 output to my 2003 server
and didn't see anything significant. Only real difference was a
nondescript "rcode = SERVFAIL" instead of NOERROR. Pretty worthless,
but maybe you can glean something from the results that I missed:
==================================================microsoft.comServer: xxx.xxxxxx.com
Address: xxx.xxx.xxx.xxx
------------
Got answer:
HEADER:
opcode = QUERY, id = 78, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion,
recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0
The Servfail is saying that it could not get the response from the server it was using, and NXDDOMAIN is saying the domain doesn't exist. It sounds like the query is not passing through or returning through a firewall. What type of firewall are you using? Is UDP53 permitted through it? But you said set vc did not work either? Canyou describe your setup a little, please?
Ace
.
- Follow-Ups:
- References:
- Forwarders cannot be validated and recursive query fails
- From: Bennett
- Re: Forwarders cannot be validated and recursive query fails
- From: Ace Fekay [Microsoft Certified Trainer]
- Forwarders cannot be validated and recursive query fails
- Prev by Date: DNS - NSlookup 'DNS Reqest timed out' for 2 sec with FQDN
- Next by Date: What aging/scavenging do?
- Previous by thread: Re: Forwarders cannot be validated and recursive query fails
- Next by thread: Re: Forwarders cannot be validated and recursive query fails
- Index(es):
Relevant Pages
|
