Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 760
  • Last Modified:

Workstations (Win7) not pointing to new DNS server

I setup a new primary DC with server 2008 and moved all FSMO roles as well as DNS and DHCP to it. However, all my workstations (Win7) are still pointing to the old DC for DNS and since it's not available, they're picking up DNS from the secondary DC.

All DNS records in my new Primary DC appear to be correct and the server is showing no errors. So how do I get my workstations to point to the new DC for DNS?
0
lenivan
Asked:
lenivan
1 Solution
 
quinnjudgeCommented:
Are the DHCP options pointing to the new DNS server IP address?
0
 
ConUladhCommented:
Did you try a ipconfig /flushdns and a release and renew on the workstations.

Any chance there is any stray routers with DHCP switched on? Even wireless routers?
0
 
Darius GhassemCommented:
Make sure you have made the changes in the DHCP scope. You can check to see what DHCP server is giving out the leases by doing a ipconfig /all on client then look for DHCP server see what IP address the lease is coming from
0
Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

 
Darius GhassemCommented:
Or do ipconfig /release and ipconfig /renew
0
 
lenivanAuthor Commented:
DHCP is pointing to the new DNS/DHCP server correctly.

I tried flushdns and renewing the IP, but it still points to the old DNS server.
0
 
lenivanAuthor Commented:
Well, it looks like the problem was my DHCP option was pointing to the old DNS server. Now my only question is how do I flush the DNS for all workstations on my network simultaneously?
0
 
Darius GhassemCommented:
Can't once you get the DHCP scope option setup right and then renew the IP address the DNS will change properly.
0
 
TravisTCommented:
You will need to do a /release firsts, then a /renew
0
 
Iain MacMillanIT ManagerCommented:
you could have your users activate a batch file, but chances are they won't have local admin rights to execute it.

best suggestion would be to shut down the systems (end of work day), then delete all the records for the Win 7 systems on DHCP server.  As soon as they are powered up and sitting at the login screen, it will have to go off and talk to the DC and DHCP server to confirm its address, and immediately renew, with the new scope details.  You could also set you Lease Duration to one day, to force every system to renew (normally set to 7 or 8 days).
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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