pods cant resolve dns from external dns server
See original GitHub issueUbuntu Server 22.04 microk8s enable dns
pods can ping ips of the network but cant resolve dns names in the network.
from node host i can resolve external dns correctly.
-- inside pod---
(ping to external dns ip)
# ping 10.58.20.1
PING 10.58.20.1 (10.58.20.1) 56(84) bytes of data.
64 bytes from 10.58.20.1: icmp_seq=1 ttl=127 time=0.487 ms
(ping to external dns name)
# ping dc01
ping: dc01: Name or service not known
# ping dc01.lab.local
ping: dc01: Name or service not known
# cat /etc/resolv.conf
search app.svc.cluster.local svc.cluster.local cluster.local lab.local
nameserver 10.152.183.10
options ndots:5
root@app-api-6d7f865754-9zcdg:/opt/app/api#
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Resolving external domains from within pods does not work
It's only from within the pods that the resolution is failing meaning I cannot communicate with the Internet from within the pods. This...
Read more >Pods can not resolve hostname from external DNS server
I have dns server on my local network and ingresses are resolved from this server. The problem is pods work inconsistent. Sometimes they...
Read more >Debugging DNS Resolution - Kubernetes
Create a simple Pod to use as a test environment · Check the local DNS configuration first · Check if the DNS pod...
Read more >DNS Failures on Kubernetes – Runbooks - GitHub Pages
If the issue is happening on all pods, there is a chance all the pods have incorrect DNS config, so this may also...
Read more >Troubleshoot DNS failures with Amazon EKS - AWS
Resolution · Verify that the kube-proxy pod is working · Connect to the application pod to troubleshoot the DNS issue · Get more...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I tested this in Ubuntu Server 20.04.4 and no problem i can run apt-get update from my container and resolve correctly with my pods, looks like problem in 22.04 not mature enough
I did that for sure. But then:
But more interesting my dns server is 10.0.0.1.