Dynamic DNS update is not happening after switching between LAN to Wi-Fi or vice-versa

Mohd Arif 946 Reputation points
2023-09-05T06:56:14.22+00:00

I have AD, DHCP and DNS roles installed on the same server. If client connect to Wi-Fi then DNS IP is registered but if the same person switch to LAN, then IP is not updated in DNS server, still we get response from old Wi-Fi IP. We have different IP range for LAN and Wi-Fi. But, not clients are facing this issue, it comes for random users. I have enabled following options

  • Dynamic update registration credential is added a service account across all servers
  • Enable DNS dynamic updates according to the settings below and Always dynamically update DNS A and PTR records are selected
  • Discard A and PTR records when lease is deleted is selected
  • DNS zone is AD integrated and secure update is enabled

Please help provide some useful ans.

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Windows for business | Windows Server | User experience | Other
Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2023-09-06T06:59:39.2933333+00:00

    Hi.

    I want to explain to you the trigger conditions of the dynamic:

    1.When you start the machine.

    2.When the terminal obtains the IP address (manually written or assigned by DHCP).

    3.changed the IP address.

    4.The domain name to which the NIC is connected is changed.

    Here are some possible solutions you can try:

    1.when you switch to LAN,Please disconnect or disable WiFi.

    2.Flush the DNS cache on both the server and the client machines. You can do this by running the command" ipconfig /flushdns " and " ipconfig /registerdns "in the Command Prompt (run as Administrator).

    3.Check the TCP/IP4 settings on the client machines. Make sure that they are set to Obtain DNS server address automatically and that they are reporting to DNS.

    4.Check the DHCP settings on the server. Make sure that the lease duration is not too long and that the scavenging interval is enabled.

    Hope the information is helpful.

    Best Regards,

    Hania Lian

     

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.