Discussion Locked

DNS Monitoring; self query fails

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When I attempt to run a test query from the DNS console (simple or recursive) on both my primary DNS zone server and my secondary DNS zone server, it fails. However, I can use nslookup from all nodes with 100% success for both forward and reverse lookups of all clients on the network.

Note: this is a small lab consisting of six clone boxes.
1 NT4 PDC
1 W2K member (DHCP)
1 W2K member server (DNS-primary)
1 W2K member server (DNS-secondary)
1 W2K member workstation
1 W2K member server
DNS client and server services are running, there is nothing in the event log to indicate a problem.
What am I missing in the DNS config?

4 replies

by deltree

Also, the primary zone is configured as a root zone, and I did verify the presence of the 1.0.0.127.in-addr.arpa reverse lookup zone

by stevej

Did you happen toenable your clients to use DNS ans list your DNS servers in your TCP/IP settings on the client machines?

If not either this information up manually or configure your DHCP server to automatically configure your clients for you

Good Luck,
SteveJ

by deltree

The DHCP service is assigning the primary DNS server. I did forget to add the secondary to the list. But this doesn't fix the issue. It is only on the DNS servers themselves that I can't run a self query from the DNS console. I can use nslookup on the DNS servers just fine. Its ONLY from DNS console where the self test fails.

This discussion is closed to new replies.