[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 489
  • Last Modified:

Verify DNS server is running normally or needs to be optimized

Is there a way to verify if DNS is working as it should be  or if needs to tweaked in some way?  I'm also going to be doing the same thing to DHCP.

This is on a SBS 2003 server.
1 Solution
Venugopal NCommented:
Run the command NSLOOKUP to check the DNS is working properly
Venugopal NCommented:
Refer the below link for how to use the NSLOOKUP command to verify DNS

You can use NSLOOKUP http://support.microsoft.com/kb/200525
and or NETDIAG that I refered to in a previous question
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

As long as you are not getting a lot of messages that indicate that name lookup failed you should be O.K.

How big is your network?
I'll go with the nslookup, and make sure that you're using your server.
Along with nslookup you can also check the DNS section in the server event viewer :)
I saw both of your questions on DHCP and DNS monitoring.

It looks like you are really trying to monitor Domain health. There are utilities that is a part of the 2003 server support tools to do just that.

For DHCP, (specifically), you can use DHCPloc.exe. That acts as a client and goes out to the domain to request a DHCP address from any available DHCP server. This is a great way to diagnose for rogue DHCP servers. A rogue DHCP server is defined as a DHCP server on your domain that is providing DHCP and wasn't authorized by you. To be more precise, it is defined as a DHCP server that is servicing the same scope and address pool as your authorized DHCP server that is on your SBS machine.

What many of the experts are eluding to is either DHCP works or it doesn't. That's pretty much true. If you have  a rogue DHCP server, your DHCP server will stop providing DHCP. If DHCP server isn't working or is blocked by a firewall, your clients will fail to get a DHCP address and therefore fail to communicate.

For DNS, (specifically), you could use NSlookup as KCTS advised.

For domain controller and networking diagnostics, you can use DCdiag  and Netdiag. DCdiag and Netdiag will get to the roots of DNS as well. It will not diagnose DHCP as you might wish.

You can go to the command prompt and type:
DCdiag /v      (meaning DC diagnostics utility Verbose)
Netdiag /v     (meaning network diagnostics Verbose)

NOTE: Both DCdiag and netdiag take a trained eye to decipher on some occasions. So, if you are having an issue, you could use experts help on EE to help you decipher what DCdiag and Netdiag are telling you.
Bottom line is, there are a lot of great utilities already built in to diagnose and monitor your system>

Another great utility is event logs. Event log entries in the 4000's, (like 4005 and 4015) are DNS related issues.

Event log entries in the 1000's are either memory leaks(, DHCP or Netbios related issues).

So fixing Event log errors will greatly help you in configuring your domain for optimum performance.

The best way is run dcdiag /test:dns & check the dns event viewer.
Nslookup,dnscmd,dnslint are the dns tool which are used for troubleshooting dns.
Nslookup is used to resolved dns names on domain.
There is lot more you can do with dnscmd & dnslint.
Below is also a good tool.
For dhcp i can find netsh dhcp cmd.
I personally feel ADmanager is good tool.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now