# Dns not resolving .cluster.local

**URL:** <https://discuss.kubernetes.io/t/dns-not-resolving-cluster-local/19144>\
**Category:** General Discussions\
**Tags:** coredns, network\
**Created:** [February 21, 2022, 7:40pm UTC](https://discuss.kubernetes.io/t/dns-not-resolving-cluster-local/19144 "2022-02-21T19:40:28Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Vajravelu\_Mani](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/vajravelu_mani/32/17506_2.png) [@Vajravelu\_Mani](https://discuss.kubernetes.io/u/Vajravelu_Mani)\
**Post date:** [July 22, 2025, 12:09pm UTC](https://discuss.kubernetes.io/t/dns-not-resolving-cluster-local/19144/7 "2025-07-22T12:09:42Z")

</div>

Hey i have exactly opposite problem.

> [@Kubernetes pods not resolving with service.namespace subdomains](https://discuss.kubernetes.io/t/kubernetes-pods-not-resolving-with-service-namespace-subdomains/32784):
>
> Asking for help? Comment out what you need so we can get more information to help you! Cluster information: Kubernetes version: v1.31.0 Cloud being used: bare-metal Installation method: minikube Host OS: Ubuntu 24.10 WSL on Windows 11 Enterprise CNI and version: calicoVersion=“v3.28.1” CRI and version: docker://27.2.0 I am running 2 pods busybox and nginx in the namespace called webcn have exposed the nginx pod as a service i am trying to understand working of name resolution in kubernetes within a namespace from busybox pod vajra@ubuntu-minikube:~/kubernetes-learn$ : kubectl get…

---

_[View the full topic](https://discuss.kubernetes.io/t/dns-not-resolving-cluster-local/19144)._