After SQL Server 2019 Availability Group failover, I need to wait half hour to connect database by available listener ip from client

After SQL Server 2019 Availability Group failover, I need to wait half hour to connect database by available listener ip from client. There are the following servers in this case: - node1, node2, AD-server (same subnet) - client (different subnet) - node1 and node2 are always on nodes which uses AD user as login The case happens when failover - node1 can connect to the database by available listener ip - node2 can connect to the database by available listener ip - AD-server can connect to the database by available listener ip - client can't connect to the database by available listener ip (also can't telnet) After half hour, client can connect database by available listener ip (also can telnet) I suspect the case is caused by DNS. Anyone have the same experience? There are some solution I tested but didn't solve the problem: - I tested MultiSubnetFailover=True and RegisterAllProvidersIP=0. - Recreate dna A record for both the available listener and cluster with “Allow any authenticated user to update DNS record with the same owner name". - https://www.pythian.com/blog/availability-group-delay-with-listener-connectivity-after-failover