server 2019 DNS clients not updating when a listener in a SQLavailability group switches

Hi Everyone,

We are running a 2012 DC with 2012 and 2016 clients connecting. I recently done a POC whereby I had  4 server configured with server 2016 connecting to a 2012 DC. 2 of the server was configured with sql 2019 running availability groups/Listener. The other two was client machine writing to the SQl 2019 DB. When the server running the primary DB in the listener gets rebooted the listener auto detects this and immediately switches the inactive to active. This is observed successfully from the windows clients side running window server 2016 and there is no break in service when writing to the DB. There is a second or two drop and when pinging the listener name and then it responds with the new IP (New active listener IP) - this scenario works perfect.

The exactly same setup above using windows 2019 server on the 4 servers and still connecting to a 2012 DC results in connectivity lost when the server running the active node in the availability group is rebooted.  Some test performed is that when the listener IP is pinged at this point it responds with the inactive node IP.  Only once a ipconfig /flushdns is performed it responds with the active IP.

Like I said further up this is not observed with the POC running windows 2016 server.

Any ideas will be great. Taariq