Windows 10 DHCP and DNS

I have never noticed such problem. It could be that it's not Windows 10 related.

No

Disable Ipv6 on windows 10 machine for time being and see if that's make any difference

Are you flushing out the DNS entries before obtaining a new lease? Is there any static settings in the advanced section of DNS or IPV4 settings on the network adapter? As Mahesh stated, uncheck the IPV6, it causes issues trying obtain and communicate and have in the past it dominate the connection and IPV4 not work in regards to LAN device resolution.

more detail is needed since it does not seem right.

Question do you have both ipv4 an IPv6 defined on the DHCP server, do they have the same lease times?

Presumably you checked that you are not oversubscribed, meaning more computers than IPs.
When the lease expires the system should have renewed the IP it was first assigned long ago.
If the lease expires something else is going on.

if you have a mix of ipv4/ipv6 with different lease expiration times, that might interfere.....

One option is to have wireshark or ms network tool, to capture events from a single windows 10 system to it dealing with dhcp requests to see what might be going on.

Do you have vlaned switches, 802.1x? etc.?

Hi Sarah2000

The your DHCP give the clients only the server IP itself as DNS or a second "external" DNS Server IP? (like 8.8.8.8 for google as example)

regards
Thomas

Our DHCP is configured only for IPv4 not for v6. The DHCP lease time is seven days.
The new Windows 10 PC are default installation, in this case both IPv6 and 4 are enabled at the adapter.
DHCP is giving only the ip of internal (AD-integrated) DNS server.
We have 802.1X enabled at switches.
Strange, It is updating the DNS recored for  Windows 7 PC immediately wether the  adapter is enabled for ipv4 or both. Fro Windows 10, it takes hours or day.

HI Sara2000

Maybe your WIndows 10 needs additional configuring to authenticate to 802.1x.
I found a good manual how check:
https://www.virtualizationhowto.com/2018/12/configure-windows-10-for-802-1x-user-authentication/
check the second part, before and with the screenshots.

Maybe they are not authenticated correctly therefore not allowed to update the DNS or something like this. I do not have enough experience with 802.1x auth, but thats where I would start to look.

Maybe also check the windows 10 eventlog, maybe there is an error or warning right after the Windows client received its IP Address.

regards
Thomas

I disabled the IPv6 at the pc's adapter and noticed the DNS update was happened immediately.
Is it something advisable to disable IP 6 at adapter level on new Windows OS?

Advisable to disable IPv6? No, if you don't have problems...Does it hurt to disable it? No, for Windows Clients.

Points to Mahesh

Please clarify your situation.
Is the issue that DNS entries disappear?
I.e. Scavenged on the DNS server, but when the lease is renewed the DNS is not updated?

When there is a change on the network interface setting, the DNS updates.?

Arnold,
is the issue that DNS entries disappear? NoI.
Scavenged on the DNS server, but when the lease is renewed the DNS is not updated? Yes
When there is a change on the network interface setting, the DNS updates.? If i uncheck  ipv6 at the adapter

Check advanced settings on the IPv4/IPv6 respectively whether they are set to register ...

Often, the registration, updates to DNS are set n the DHCP from the old days where client updates of DNS records were not reliable.

Would it not be the case that both of the first two answers to the questions posed is yes.
Following scavenging, DNS entries disappear and are not updated when the client lease for ip is renewed.

Check the DHCP settings/properties dealing with whether the DHCP server is configured to register IPs it allocates in DNS.