Cluster information: Kubernetes version: v1.23.1 Cloud being used: bare-metal Installation method: kubeadm Host OS: Ubuntu 20.04 CNI and version: Flannel CRI and version: cri-o v1.23.1 Hi Everybody, I am having some strange DNS issues with a fresh cluster setup. I am not able to resolve pods…

Could you please paste here the output of: kubectl get cm coredns -n kube-system -o yaml

Sure, here is the output: apiVersion: v1 data: Corefile: | .:53 { errors health { lameduck 5s } ready kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure fallthrough in-addr.arpa ip6.arpa ttl 30 …

@cneumaier i have the save problem since i upgrade my k8s from 1.24 to 1.27 did you find a solution ? thanks for your return

I solved this problem by editing the coredns ConfigMap: apiVersion: v1 data: Corefile: | .:53 { errors health { lameduck 5s } ready kubernetes cluster.local cluster.local.localdomain in-addr.arpa ip6.arpa { pods insecure …

Hey i have exactly opposite problem. [image] Kubernetes pods not resolving with service.namespace subdomains General Discussions Asking for help? Comment out what you need so we can get more information to help you! Cluster information: Kubernetes version: v1…

Dns not resolving .cluster.local

General Discussions

Vajravelu_Mani July 22, 2025, 12:09pm 7

Hey i have exactly opposite problem.

Topic		Replies	Views
Kubernetes pods not resolving with service.namespace subdomains General Discussions minikube , coredns , network	2	332	August 3, 2025
Dns not resolving .svc.cluster.local only .svc General Discussions coredns	0	1693	August 2, 2023
Unable to resolve pod to pod (coredns) General Discussions coredns	3	4358	August 13, 2020
Coredns name resolution issue in kubeadm clutser microk8s network	0	190	March 26, 2024
Issue with resolving external name from pod General Discussions network	2	106	October 11, 2025

Dns not resolving .cluster.local

Related topics