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.
LVL 2
ccallisonAsked:
Who is Participating?
 
Pete LongConnect With a Mentor Technical ConsultantCommented:
AD is 99.9% dependant on DNS, either set up scavenging on your forward lookup zone or manually delete the old entry.
0
 
Pete LongTechnical ConsultantCommented:
whats in your DNS forward lookup zone?
0
 
Pete LongTechnical ConsultantCommented:
i.e. is there an entry for the WRONG IP address?
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

 
Pete LongTechnical ConsultantCommented:
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
 
Pete LongTechnical ConsultantCommented:
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
 
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 LongTechnical ConsultantCommented:
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
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.

All Courses

From novice to tech pro — start learning today.