coredns: i/o timeout when set upstream
When i set a upstream dns server, i find the dns solved is slow, and the log of coredns pod is :
[ERROR] 2 mirrors.unisound.ai. AAAA: unreachable backend: read udp 10.99.17.97:60877->10.10.10.252:53: i/o timeout
AFAIK, many people meet the error. @chrisohaver Can you help me ?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 20 (9 by maintainers)
i encountered the same problem i use kubeadm to start the cluster, everything is fine but CoreDNS pod can’t resolve the service name from DNS
same here, can we re-open this issue

Note that
dig
does not follow search list in/etc/resolv.conf
by default, you need to pass the+search
option for it to do that.@JadeRing I was facing the same issue as you were, I was able to resolve this by configuring
/etc/netplan/50-cloud-init.yaml
on theworker node
and setting the nameserver to ‘8.8.8.8’ instead of my192.168.1.1
.I think the issue could be that the pods are on a different subnet and are not able to access my DNS on 192.168.1.1.
another potential issue could be this known issue regarding some distros (Ubuntu) and the
--resolv-conf
flag