Bug: IPv6 Only Cluster fails to resolve svc.cluster.local addresses #1038

Closed
opened 2026-04-05 16:25:02 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @xorl on 4/21/2024

Describe the bug
When deployed on an IPv6 only cluster, the app pod cannot resolve svc.cluster.local addresses as it expects an A, not a AAAA.

Error: getaddrinfo ENOTFOUND platform-oneuptime-redis-master.oneuptime.svc.cluster.local
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -3007,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'platform-oneuptime-redis-master.oneuptime.svc.cluster.local'
}

To Reproduce
Steps to reproduce the behavior:

  1. Deploy iPv6 only cluster
  2. Configure redis to bind on * and -::*
  3. Restart -app pod.
  4. See error

Expected behavior
When deployed, service should be able to to resolve AAAA addresses.
Addresses obfuscated below.

➜  kubectl -n oneuptime exec -i -t dnsutils -- nslookup platform-oneuptime-redis-master.oneuptime.svc.cluster.local
Server:		<obfuscated>
Address:	<obfuscated>#53

*** Can't find platform-oneuptime-redis-master.oneuptime.svc.cluster.local: No answer

➜  kubectl -n oneuptime exec -i -t dnsutils -- nslookup -q=AAAA platform-oneuptime-redis-master.oneuptime.svc.cluster.local
Server:		<obfuscated>
Address:	<obfuscated>#53

platform-oneuptime-redis-master.oneuptime.svc.cluster.local	has AAAA address <obfuscated>

Screenshots

Deployment Type
self-hosted - EKS (kubernetes)

*Originally created by @xorl on 4/21/2024* **Describe the bug** When deployed on an IPv6 only cluster, the app pod cannot resolve svc.cluster.local addresses as it expects an A, not a AAAA. Error: getaddrinfo ENOTFOUND platform-oneuptime-redis-master.oneuptime.svc.cluster.local at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26) at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17) { errno: -3007, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'platform-oneuptime-redis-master.oneuptime.svc.cluster.local' } **To Reproduce** Steps to reproduce the behavior: 1. Deploy iPv6 only cluster 2. Configure redis to bind on * and -::* 3. Restart -app pod. 4. See error **Expected behavior** When deployed, service should be able to to resolve AAAA addresses. Addresses obfuscated below. ``` ➜ kubectl -n oneuptime exec -i -t dnsutils -- nslookup platform-oneuptime-redis-master.oneuptime.svc.cluster.local Server: <obfuscated> Address: <obfuscated>#53 *** Can't find platform-oneuptime-redis-master.oneuptime.svc.cluster.local: No answer ➜ kubectl -n oneuptime exec -i -t dnsutils -- nslookup -q=AAAA platform-oneuptime-redis-master.oneuptime.svc.cluster.local Server: <obfuscated> Address: <obfuscated>#53 platform-oneuptime-redis-master.oneuptime.svc.cluster.local has AAAA address <obfuscated> ``` **Screenshots** **Deployment Type** self-hosted - EKS (kubernetes)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#1038