techsolve1
asked on
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
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
ASKER
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
Thanks
ASKER
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
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
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
ASKER
How long should the records take to populate?
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.
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.
ASKER
Thanks, if that fails any other advice!?
Lets cross that bridge if we come to it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
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
ASKER
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
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
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.
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.
ASKER
Hi Appoloogies
Footech should be awared points, an oversite on my part
Footech should be awared points, an oversite on my part
Absolutely right,
Footech should be awarded will full points
Footech should be awarded will full points
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