Domain server DNS problem

Hi all

I have a problem with a single server domain 2008 r2, where someone has decided to change the IP address, dhcp scope and subsequently mess up the DNS server, and then proceed to delete DNS from the server
I have added DNS back but obliviously it's not working and the domain has ground to a halt
What is the procedure to fix the DNS and domain from these mistakes
Thanks in advance
techsolve1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RizzleCommented:
Can you elaborate on the problem as the initial description is abit too vague.

Have you re-added and restored the other services?

Can you confirm all the steps in the below guide have been followed.
https://technet.microsoft.com/en-us/library/cc725925.aspx
To ensure your DC can be located by your clients start off by re-registering the SRV records.
http://support.microsoft.com/kb/556002
0
techsolve1Author Commented:
The roles haven't been removed, just the DNS forward and reverse zones have been deleted, I have registered the SRV roles but when you run nslookup you get unknow server and no IP address as you would expect, would it be best to remove the roles and re install them and start again?

Thanks
0
techsolve1Author Commented:
The static IP of server was changed to a different one, ie 192.168.10.xxx to 172.16.12.xxx and dhcp scope modified to same
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

RizzleCommented:
Yes it worth a go!

But before you try that do the following

Run dnscmd /clearcache

Then

Ipconfig /registerdns

Then reboot the server and allow time for the DNS records to populate
0
techsolve1Author Commented:
How long should the records take to populate?
0
RizzleCommented:
If you want replication to occur immediately instead of waiting for the typical replication cycle, follow these steps:

In Administrative Tools, start Active Directory Sites and Services.
Expand Sites. There should be at least one site labeled "default-first-site-name" (or others if they have been manually configured).
Expand default-first-site-name, expand Servers, and then expand Computer.
Expand NTDS Settings. One or more objects are listed in the right pane. One of those objects is a link to the domain controller you want. To see the "friendly" name, right-click an entry and view the name. One of the objects points to the domain controller you want. Right-click that entry, and then click Replicate Now. The replication is performed immediately.
0
techsolve1Author Commented:
Thanks, if that fails any other advice!?
0
RizzleCommented:
Lets cross that bridge if we come to it.
0
footechCommented:
Not sure what roles you're thinking of removing, but if this is your only domain controller, you certainly don't want to remove the AD DS role!

Have you adjusted your NIC settings so they point to a valid (internal) DNS server?
You should be able to create new forward lookup zones
 - yourdomain.com (or whatever the name of your domain is).  Set replication to "all DNS servers in the domain", AD-integrated, dynamic updates to secure only
 - _msdcs.yourdomain.com - Set replication to "all DNS servers in the forest", AD-integrated, dynamic updates to secure only

Then restart the Netlogon service
net stop netlogon && net start netlogon

The DC should then re-register its records automatically.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MaheshArchitectCommented:
Agreed with footech

Just point your server to itself own IP (not 127.0.0.1) as preferred DNS in tcp/ip settings and then recreate domain.com AD integrated zone and then restart netlogon and dns server service and you should be back in business
0
techsolve1Author Commented:
Hi All
Update
DNS functioning ok now, but server slow to finish logging in completely, and clients are hit and miss recieveing a dhcp address, when they do finaly get on by manually ipconfig /renew everthing works fine
DNS forward and Reverse lookups are fine
ideas!?
Thanks
0
footechCommented:
As this is a different problem than your original question, you're probably best off to start a new question.

Sounds a bit like a networking issue.  Try ping tests, examine server logs, maybe do some network captures, make sure the server's not overloaded.
0
techsolve1Author Commented:
Hi Appoloogies
Footech should be awared points, an oversite on my part
0
MaheshArchitectCommented:
Absolutely right,

Footech should be awarded will full points
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

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.