Even though in DHCP Address Leases its showing the proper IP.
I tried /flushdns on all computers (mine, the client, and the server) and I get the same results when pinging that computer.
I just noticed this is also causing Event ID 4 to appear in the log of the server: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server WXP-ALVINM$. Commonly, this is due to identically named machine accounts in the target realm (MACMACHINE. You are right it does seem to be my computer that's keeping the old records.
The strange thing is the server that assigns the DHCP addresses is also pinging the wrong IP address.
Leases are retained in the DHCP server database approximately one day after expiration.
This grace period protects a client's lease in case the client and server are in different time zones, their internal clocks are not synchronized, or the client is off the network when the lease expires.
I believe there are two ways to solve this: You can either join your Linux machines to Active Directory using SAMBA and then they should be able to update their DNS records (if I recall correctly just being a domain member is enough to be able to update secured DNS zones) or your Windows admin can configure a "proxy-account" that will be used to authenticate when performing the secured updates.
Create an Active Directory user and make sure that it is a member of the Dns Update Proxy.Under Windows NT, DNS was static and had to be manually altered to make changes.With the advent of Windows 2000, many administrators were elated to hear that it contained a new feature called Dynamic DNS (DDNS).I have an odd DNS issue that only sometimes presents itself.I have several Linux machines, running Ubuntu (10.10, 11.10, 12.04). Sometimes, however, the system gets an IP address from DHCP, but fails to update the DNS server with it's hostname and IP.For those companies considering an upgrade to Microsoft Windows Server 2008, it is very important to understand how DHCP and DNS work together to power Windows Server 2008.