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

Windows 2003 server assigning incorrect (old) DNS server IP via DHCP

Small problem with a Windows 2003 server running DHCP.  I recently needed to remove one of the two Domain Controllers in this network.  The DHCP server on the remaining Domain Controller was originally configured to assign both itself and the other DC as DNS servers with the other DC as the primary DNS server.

I've reconfigured the DHCP scope, removing the old DC as the primary DNS server but about 50% of the time on boot the client PC's seem to still set it as the primary DNS server.  

I have not rebuilt the DHCP scope from scratch as there are multiple reservations and I'd prefer not to have to do this but I'm at a loss for where the client PC's are pulling the old DC as the primary DNS server from.

How can I resolve this issue?
0
winningtech
Asked:
winningtech
  • 2
1 Solution
 
KCTSCommented:
The clients will retain the old information until the lease is renewed, if you want to force this then run the ipconfig /renew command on the clients, they will then renew the lease and get the new DNS server info.

It might also be worth chacking that come lients have not got the DNS server assigned satatically.
Alpo check that the DNS is not being assigned differently on the reservations. (You can assign options at the server level, scope level and reservation level - make sure there are no conflicts)
0
 
winningtechAuthor Commented:
I'll doublecheck the reservations.  As far as doing the ipconfig /renew I've done this on a few PC's when they've retrieved the wrong DNS settings.  Renewing the IP address causes them to obtain the correct DNS IP address.  My issue is when the PC's are rebooted they revert to obtaining the old DNS server IP address.

I've verified that regardless of which DNS server they're getting they get it from the same DHCP server (which is also the Domain Controller and DNS server).  

Am I missing something in Group Policy or DNS on the Domain Controller which might be causing the workstations to revert to the older server for DNS?
0
 
Hypercat (Deb)Commented:
Make sure that you don't have options set at both the scope and server level.  If you have both, then the scope level options will override the server options. So, if you have scope options set for the old DNS server and server options set for the new, that could be the problem.
0
 
winningtechAuthor Commented:
I think I've resolved this.  I found that the old DC still had a deauthorized DHCP scope but that the server was still authorized.  I was unable to unauthorize the server so, as I no longer need DHCP on this server, I uninstalled DHCP.  On the off chance that the problem reoccurs I also configured DNS secondary zones on this server and configured DNS replication from the DC to this server.  

Thanks for the advice.  Both answers made me wonder if there might have been another DHCP server somewhere on the network.  
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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