DNS resolution failed

[J1a-wei]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

3.1 DBLess

Current Behavior

Upgrade kong through helm. The version is upgraded from 2.7 to 3.1. The custom plug failed to connect to Redis.
Redis package kong
Env: EKS 1.21

try_hosts_slots(): unable to connect, attempt nr 1 : error: [cosocket] DNS resolution failed: dns client error: 101 empty record received. Tried: ["(short):(na) - cache-miss",".kong.svc.cluster.local:33 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".svc.cluster.local:33 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".cluster.local:33 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".ap-northeast-1.compute.internal:33 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",":33 - cache-hit/dns client error: 101 empty record received",".kong.svc.cluster.local:1 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".svc.cluster.local:1 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".cluster.local:1 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".ap-northeast-1.compute.internal:1 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",":1 - cache-hit/dns client error: 101 empty record received",".kong.svc.cluster.local:5 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".svc.cluster.local:5 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".cluster.local:5 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",".ap-northeast-1.compute.internal:5 - cache-miss/scheduled/querying/try 1 error: bad name/scheduled/querying/try 2 error: bad name/dns lookup pool exceeded retries (1): bad name",":5 - cache-hit/dns client error: 101 empty record received"], client: 100.168.55.84, server: kong, request: "GET /ethereum2/prater/eth/v1/beacon/states/head/validators?id=0x80e528042cea5962e56b7a9840072ef86716a85a8e4ad321527cd40c1ab10415135e44803862f520c58933e7d089354a HTTP/1.1"

Expected Behavior

No response

Steps To Reproduce

No response

Anything else?

No response

[surenraju-careem]

Related issue #9959

[ghost]

Related issue #9959

I think the key error in the feedback for this issue is bad name