Go Premium for a chance to win a PS4. Enter to Win

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

Old IP address of AD DHCP server keeps returning when I open the DHCP MMC....

Can someone please tell me where this value resides in AD?  I've unauthorized and re-authorized my DHCP server just like the MS Q-note suggests and the server continues to pop up with the old IP address when I use the "Manage authorized servers".  (btw, it shows two entries for the server; one correct and one old).  It happens even when I am on a machine where I have never used the DHCP MMC, so it's not a locally saved value.

I've tried searching the AD database using ADSI, but no luck so far.  More of an annoyance than anything else.
0
ccallison
Asked:
ccallison
  • 6
  • 3
1 Solution
 
Pete LongConsultantCommented:
whats in your DNS forward lookup zone?
0
 
Pete LongConsultantCommented:
i.e. is there an entry for the WRONG IP address?
0
 
Pete LongConsultantCommented:
also make sure this reg key (on the DHCP server) has a value of 1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DisableDynamicUpdate

0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

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.

 
Pete LongConsultantCommented:
oops wrong! should have a value of 0
0
 
ccallisonAuthor Commented:
I think you're way off, Pete.  The DHCP server is the DC and it is correctly registering itself in DNS, both forward and reverse.  There are two entries listed,  both with the name of the DHCP server - one is the correct new address and one is the incorrect old address.  It is being queried by the DHCP MMC tool from somewhere in AD, not DNS.
0
 
Pete LongConsultantCommented:
AD is 99.9% dependant on DNS, either set up scavenging on your forward lookup zone or manually delete the old entry.
0
 
ccallisonAuthor Commented:
Scavenging is already turned on for all forward and reverse zones and there IS no old entry.  DNS is correct.  I have run both DCDiag and Netdiag and found no errors.  AD is highly dependent on DNS as a locator service for many functions( finding PDC, GS, site subnet assignments, etc.), but the admin tools often query the AD database through LDAP directly.
0
 
ccallisonAuthor Commented:
Okay, I found a way to remove the old entry, but it still doesn't satisfy my curiosity as to where this value was being held.

In the DHCP MMC, if you have the correct address open and under management, then reselect "Manage Authorized Servers" and then highlight the offending entry with the legacy address and select unauthorize.  It doesn't seem to affect the running service on the new address.
0
 
Pete LongConsultantCommented:
comment from pete 04/01/04 0436 hrs GMT: or manually delete the old entry
reply >>there IS no old entry
2nd reply >>Okay, I found a way to remove the old entry

Bizaare
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

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