dstjohnjr
asked on
How to rebuild DNS on Active Directory Windows Server 2008 R2
Hello Experts - I am having major problems with DNS in my domain. Here's the situation:
First, if you want a little history - see the below issue, in which I have been successful in seizing the roles on my current DC since my previous DC died.
https://www.experts-exchange.com/questions/27871018/Windows-Server-Domain-Controller-Issues.html
However, when I am trying to bring a 2nd DC online, it is unable to find the PDC.
Here the main problem:
When I ping "hostname", it resolves, but when I ping "hostname.domainname.local " it doesn't resolve. How can I rebuild the DNS on my PDC the way it's supposed to be? Is there some sort of command line tool I can run?
Thanks in advance for any help to help me rebuild DNS on my PDC Windows Server 2008 RS installation!
EDIT: As a followup since I posted - on my 2nd DC which I am trying to introduce into the domain (as a 2nd DC), I added a "hostname.domain.local" (with corresponding IP address) into the "hosts" file in /windows/system32/drivers/ etc and now things are coming alive on the 2nd DC. But... I know this shouldn't be how it is. Again - looking for a way to auto fix the DNS on my PDC. Thanks!
First, if you want a little history - see the below issue, in which I have been successful in seizing the roles on my current DC since my previous DC died.
https://www.experts-exchange.com/questions/27871018/Windows-Server-Domain-Controller-Issues.html
However, when I am trying to bring a 2nd DC online, it is unable to find the PDC.
Here the main problem:
When I ping "hostname", it resolves, but when I ping "hostname.domainname.local
Thanks in advance for any help to help me rebuild DNS on my PDC Windows Server 2008 RS installation!
EDIT: As a followup since I posted - on my 2nd DC which I am trying to introduce into the domain (as a 2nd DC), I added a "hostname.domain.local" (with corresponding IP address) into the "hosts" file in /windows/system32/drivers/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, all workstations are pointing at the same IP address (the current PDC) for their DNS.
Things seem to be getting better (not sure if these things just take time propagating, even internally), but I can now ping hostname.domainname.local from workstations. Not sure if the entry into the hosts file (/windows/system32/drivers /etc) had any bearing, but I'm running through some of your other suggested tests now as well to see what gives. Ideally, I'd like to alleviate the hosts entry altogether. I'll start doing these tests on my 2nd DC as that is where the issues had the most adverse affect.
Thanks so much for your help and direction!
Things seem to be getting better (not sure if these things just take time propagating, even internally), but I can now ping hostname.domainname.local from workstations. Not sure if the entry into the hosts file (/windows/system32/drivers
Thanks so much for your help and direction!
ASKER
Ok, strange. Running nslookup on the hostname and hostname.domainname.local on my 2nd DS is now returning what I expect. Guess next step is to remove the entry from my hosts file and see how it goes. :) Getting closer!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
All is well! All tests are coming back positive. I think some of this was just being patient but I did run quite a few of your commands as well. Thanks for your help!
ASKER
Thanks again for your assistance in resolving my issue!
ASKER