Connectivity Issue with pgcat after AWS Aurora PostgreSQL DB Failover

After an AWS Aurora PostgreSQL failover, the pgcat connects to the read replica and fails to automatically recover. The client expects to connect to the write replica, but the connection on pgcat remains connected to the read replica. This issue may be related to DNS cache. We need a viable solution to resolve this problem.