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

Failed domain controller still listed as DNS server

Hello Experts,

I have two servers:

PDC = Server 2008 R2 = 'Server1' = 10.0.0.1
BDC = Server 2003 - 'Server2' = 10.0.0.2

there used to be another, which failed completely (replaced by Server 2008R2)
PDC = Server 2003 = 'Server3' = 10.0.0.3

The FSMO roles were successfully transferred and all of the ADUC, ADSS, DNS entries were cleaned up to remove Server3 as per MS documentation, however when I do an NSLOOKUP of the internal domain from any of the servers and PCs on the network, the IP address of the failed 'Server3' is still listed.

Can anyone suggest where else I should check for references to this server?  

Thank you in advance!
0
fourthgen
Asked:
fourthgen
1 Solution
 
cshepfamCommented:
When you looked in DNS, did you look in the Name Servers?  If it was a DC, you can't just remove the A record, you have to go into the Name Servers and remove that instance.

Also, did you demote it correctly?  If not then there may still be metadata in place.  You can go in Sites and Services and check to see if the DC is located in there.
0
 
fourthgenAuthor Commented:
Hello cshepfam,

Yes, have removed entries from Name Servers tab in DNS.
No chance to demote it due to catastrophic RAID failure; Sites and Services has all been cleaned up according to MS documentation such as example below:

https://technet.microsoft.com/en-us/library/cc816907(WS.10).aspx?tduid=(431f15b053b4881b86cc0c79e79b7f0c)(256380)(2459594)(TnL5HPStwNw-RPn6XNAhuR1Fyrw3vxDS0A)()
0
 
footechCommented:
If the command you're running is something like
nslookup yourdomain.com
Then those results are returned by any records in the zone yourdomain.com that appear with a name "same as parent".  Those records are used to lookup a DC when a service is not site-aware (can't use the DCLocator process).  So look for a "same as parent" A record with the IP of your failed DC.
1
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
FOXActive Directory/Exchange EngineerCommented:
Have you checked for the entry in reverse lookups in your DNS as well?
0
 
fourthgenAuthor Commented:
Excellent, sorted! - I must've missed this several times when combing through the DNS entries as it didn't reference the server by name.

Thank you footech.
0
 
footechCommented:
Glad to help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

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