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

How do I locate all DNS servers?

While adding a new 2008 R2 DC the message displayed during my DNS and Global Catalog choices that there were 2 DNS servers in our Domain.  However, that isn't the case.  The new DC that I'm building actually re-building was previously a DNS server, however it was properly demoted and removed from the domain before re-build.  

I ran a scan using WSPing Pro and it only shows 1 DNS server.

So is the Windows message and error or do I have a rogue DNS server?  How do I verify?
0
J.R. Sitman
Asked:
J.R. Sitman
  • 11
  • 3
  • 3
  • +3
1 Solution
 
costanosNetwork EngineerCommented:
What shows up when you run NSlookup in CMD?
0
 
George KhairallahCommented:
Perhaps you can try doing it with nslookup?
nslookup
Set type=NS
contoso.com

Open in new window

0
 
Mike KlineCommented:
You can use nslookup


nslookup
set type = NS
Your domain name

Look on the name servers tab in DNS and look for entries for the old box in DNS.

Thanks

Mike
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
J.R. SitmanAuthor Commented:
when I run NSlookup I get "default server unknown 172.17.1.30".  which was the old DNS server that was removed but has now been added back in with the same IP and it is now a DNS server again
0
 
J.R. SitmanAuthor Commented:
if I run it from the new DNS server I get the same results but with the ip address of the other DNS server.
0
 
George KhairallahCommented:
Is your DNS configuration of that server correct?
Have you verified that this DNS server is functioning?
What is your ipconfig on your workstation like? are you able to resolve (forward and reverse) the name/IP of that server from your workstation?
If you can't, then you need to address that issue to make sure that is working.
0
 
Sarang TinguriaSr EngineerCommented:
make sure you have setup DNS correctly in your env follow below best practices

Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

Also run dcdiag /test:dns to check the DNS issue on the dc
0
 
J.R. SitmanAuthor Commented:
DNS settings verified.
Yes DNs is working.  No problems
ipconfig from the workstation shows the proper DNS servers and DHCP server

So as far as I can tell there isn't a problem, that I can see
0
 
J.R. SitmanAuthor Commented:
OK.  I'll post later.  Got to get to a meeting
0
 
J.R. SitmanAuthor Commented:
when I run dcdiag /test:dns I get unrecognized command.  I get the same thing if I run ipconfig /flushdns
0
 
DrDave242Commented:
You get "unrecognized command" when you run ipconfig /flushdns?  If that's the case, something's gone very wrong.

Wait, you're not still in nslookup, are you?  If so, type exit and try again from the normal command prompt.
0
 
George KhairallahCommented:
Also, when you're doing these commands, you might want to open the command prompt with elevated privileges.
ipconfig /flushdns will work with normal privilege, but, ipconfig /registerdns won't.
0
 
J.R. SitmanAuthor Commented:
yep was still in nslookup.  Attached are the results.  It is trying to find a DNS server that has been gone at least 2 years spcala02
dnsfail.jpg
0
 
DrDave242Commented:
Open the DNS console on one of your DNS servers, right-click your domain's forward lookup zone, and select Properties.  What's listed in the Name Servers tab?  (Check any other forward lookup zones you've got too.)
0
 
J.R. SitmanAuthor Commented:
There are 3 forward lookup zones.  see attached.  In all three the only DNS server listed is the one that was removed two weeks ago and then added back today.  I used the same server name and IP address when adding it back to the domain
dnsforward.jpg
0
 
J.R. SitmanAuthor Commented:
I just did ipconfig /all from a workstation and it has all the correct servers. DNS/DHCP
0
 
DrDave242Commented:
I just noticed that the failure occurs in the Delegations test.  Given your zone setup, there's probably only one delegation present, and that's for the _msdcs.LASPCA.CORP zone.  However, the delegation record itself will be inside the LASPCA.CORP forward lookup zone.  Open that zone and look for a record named _msdcs.  It should look like a grayed-out folder.  Right-click that record and select Properties.  In the Name Servers tab of the properties window, I'm guessing the bogus server will be listed.  If so, remove it from the list.
0
 
J.R. SitmanAuthor Commented:
yep it was.  I'll rerun the test.
0
 
J.R. SitmanAuthor Commented:
The initial rogue DNS server is gone but the other errors are still there.  I'll award the points for this and open a new case.  Please watch for it.  You obviously know what you're doing.

Thanks
0
 
J.R. SitmanAuthor Commented:
thanks
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 11
  • 3
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now