Automated Query Test Failed

  • Thread starter Thread starter Newscene
  • Start date Start date
N

Newscene

We have suddenly encountered a failure on one of our Win2000 DNS. We are
having the "Automated Query Test Failed" but we haven't found anything that
we can identify as the problem. And there is zero information in the
Knowledgebase about this problem.

The server is answering queries in the local domains but does not respond
for external lookups.

Can anyone shed some light on the problem and how we can recover from it.
 
Please ensure your forwarders are configured correctly to point to ISP DNS
and these external dns servers are able to reachable from you dns server.

With Regards,
M S Ali
 
We don't have any forwarders configured on either of our DNS. The other one
id NOT exhibiting this problem even without forwarders. These servers have
been running this way for about 6 months and this just started last week.
 
Can you check which Query is failing? Is it the simple query against your DNS
or Recursive Query to other DNS? You can check this from monitoring tab in
Properties of the DNS Server in DNS Management Console.

With Regards,
M S Ali
 
Actually both are failing.

I have removed the DNS from the machine, rebooted and then reinstalled
(along with SP4). Before rebooting I went so far as to 'scrub' the registry
of references to the DNS and removed the \system32\dns\ sub directory to get
rid of as many references to DNS as I could. After reinstalling I recreated
the zone for my primary domain and ran the test again with only the one
domain present --- both still failed, even after a fresh DNS install!

Fortunately I have two other DNSs running on-and-off site. Last week when
this nonsense started we updated the root to reflect that this is no longer
the primary DNS so at least we are not down. But we need to get this DNS
back in service because all the domains show this machine as the SOA --- and
apparently that can't be changed without removing and reinstalling each zone
individually.

Thanks
 
1. Can you think back as to what changes did you make to the server after
which it stopped working?
2. Did you notice any events logged in event log related to DNS Server?
3. Is your zone active directory intregrated?
4. What happens when you try to run nslookup on server and client? Are you
getting any error?
5. Hope you have checked your network card to be working fine with all
proper drivers and that the client are able to otherwise connect to DNS
Server.

With Regards,
M Shajid Ali
 
1. This machine also serves as the network monitor (alchemy eye) and IDs
(snort) so things change quite a bit, its hard to recall what might have
changed and when. Its also difficult to know precisely when this problem
started, by and large the DNSs run so well that we don't check them all that
often.

2. Again its hard to know as we don't have a very narrow window on the
failure.But the system is locked down pretty hard so accesses would tend to
be either difficult or stand out when they do happen.

3. One of the zones was AD integrated (our local domain) but most of the
others are client domains and were simple primaries/secondaries.

4. Failures in nslookup were one of the things that led us to take a closer
look at the DNS. Some local queries failed that should not have.

5. All of the other functions running on the system are running fine so I'd
tend to dismiss the card

The thing that is now most disturbing is that we have removed it completely
and reinstalled and it failed immediately
 
Back
Top