# Coredns Issue on Kubernetes Cluster
**URL:** https://discuss.kubernetes.io/t/coredns-issue-on-kubernetes-cluster/32179
**Category:** General Discussions
**Tags:** coredns
**Created:** [April 22, 2025, 9:31am UTC](https://discuss.kubernetes.io/t/coredns-issue-on-kubernetes-cluster/32179 "2025-04-22T09:31:14Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Savita\_Burnwal](https://discuss.kubernetes.io/u/Savita_Burnwal)
#### Post date: [April 22, 2025, 9:31am UTC](https://discuss.kubernetes.io/t/coredns-issue-on-kubernetes-cluster/32179/1 "2025-04-22T09:31:14Z")
Asking for help? Comment out what you need so we can get more information to help you!
### Cluster information:
Kubernetes version: 1.30.6
Cloud being used: bare-metal
Installation method: Kubeadm
Host OS: Ubuntu 20.0
CNI and version: Weave-net
CRI and version: Containerd - 1.6.31
Coredns pod intermittently sending domain name resolution requests to Google dns server 8.8.8.8 instead of the DNS server configured in /etc/resolv.conf. We checked the coredns configmap to check the forwarder config and it is having /etc/resolv.conf file. Most of the times it sends the request to the dns server configured in /etc/resolv.conf but intermittently it sends to 8.8.8.8 and hence the domain names configured privately gets NXDOMAIN error. We captured packets on the nodes and found out that the requests are intermittently being sent to 8.8.8.8 dns server.
---
### Author:  [@ATao](https://discuss.kubernetes.io/u/ATao)
#### Post date: [April 23, 2025, 6:39am UTC](https://discuss.kubernetes.io/t/coredns-issue-on-kubernetes-cluster/32179/2 "2025-04-23T06:39:16Z")
Maybe it have local cache exists when you changed /etc/resolv.conf of the host, Advice you can restart as follow.
1. kubelet
2. coredns