troubleshooting Question

Using nslookup and anomalies

Avatar of hypercube
hypercubeFlag for United States of America asked on
Windows 10
4 Comments1 Solution9 ViewsLast Modified:
I'm seeing some things that concern me and I'd like, if possible, to clear them up.
This is a domain-based network with 3 interconnected subnets.
All IP addresses are static and manually entered.
The local DC is the first DNS address in the list and there are 2 more DCs on each DNS list on a workstation.

I'm seeing this:
if I run nbtstat -a 10.10.10.68, I get the workstation name that I expect; call it "A".
If I ping that workstation name, I get 10.10.10.68, the address for "A".
Both as expected.

If I run nslookup, I see the local DC as the server- as expected.
If I enter >server 10.10.10.68
I get:
Default Server:"B" the name of another workstation.
Address: The address that I entered for the server 10.10.10.68.
So, these don't match!

We're using GFI Languard and it's reporting that both "A" and "B" are running DNS.
I haven't figured out why that would be.
I haven't figured out what GFI Languard is sensing to report this.
I haven't figure out how to turn off the reported workstation DNS service(?).
I only see the DNS Client running in services on all the workstations.
(All Windows 10 Pro).

Any explanations or suggestions?





Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros