# \#coredns **URL:** https://discuss.kubernetes.io/tag/coredns/37.md [Latest](https://discuss.kubernetes.io/latest.md) · [Categories](https://discuss.kubernetes.io/categories.md) · [Tags](https://discuss.kubernetes.io/tags.md) --- ## [CoreDNS is stuck in CrashLoopBackOff](https://discuss.kubernetes.io/t/coredns-is-stuck-in-crashloopbackoff/30514)
**Author:** [@SimonRelu](https://discuss.kubernetes.io/u/SimonRelu)\ **Replies:** 4\ **Last updated:** [May 11, 2026, 3:27am UTC](https://discuss.kubernetes.io/t/coredns-is-stuck-in-crashloopbackoff/30514 "2026-05-11T03:27:27Z")
hey, I have setup the following cluster with kubeadm kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-flannel kube-flannel-ds-h969m… --- ## [Core DNS in minikube](https://discuss.kubernetes.io/t/core-dns-in-minikube/34075)
**Author:** [@eugenie.kozich](https://discuss.kubernetes.io/u/eugenie.kozich)\ **Replies:** 0\ **Last updated:** [January 26, 2026, 7:12pm UTC](https://discuss.kubernetes.io/t/core-dns-in-minikube/34075 "2026-01-26T19:12:01Z")
The problem is that if I specify imagePullPolicy: Always in the manifest and run Minikube without internet access, the DNS server crashes and can’t resolve names. For example, docker@minikube:~$ ping google.com ping: g… --- ## [Microk8's three node HA cluster, odd intermittent issue with coreDNS and Pod to Pod communications](https://discuss.kubernetes.io/t/microk8s-three-node-ha-cluster-odd-intermittent-issue-with-coredns-and-pod-to-pod-communications/33075)
**Author:** [@Harry-Pottar](https://discuss.kubernetes.io/u/Harry-Pottar)\ **Replies:** 0\ **Last updated:** [August 28, 2025, 7:55pm UTC](https://discuss.kubernetes.io/t/microk8s-three-node-ha-cluster-odd-intermittent-issue-with-coredns-and-pod-to-pod-communications/33075 "2025-08-28T19:55:43Z")
I have Microk8’s three-node cluster running on AWS. I’m currently setting this up for production, but I’m free to wipe and start again, which I have done a few times in my testing. I have three namespaces. Dev UAT Pro… --- ## [Kubernetes pods not resolving with service.namespace subdomains](https://discuss.kubernetes.io/t/kubernetes-pods-not-resolving-with-service-namespace-subdomains/32784)
**Author:** [@Vajravelu\_Mani](https://discuss.kubernetes.io/u/Vajravelu_Mani)\ **Replies:** 2\ **Last updated:** [August 3, 2025, 5:20am UTC](https://discuss.kubernetes.io/t/kubernetes-pods-not-resolving-with-service-namespace-subdomains/32784 "2025-08-03T05:20:49Z")
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… --- ## [Dns not resolving .cluster.local](https://discuss.kubernetes.io/t/dns-not-resolving-cluster-local/19144)
**Author:** [@cneumaier](https://discuss.kubernetes.io/u/cneumaier)\ **Replies:** 6\ **Last updated:** [July 22, 2025, 12:09pm UTC](https://discuss.kubernetes.io/t/dns-not-resolving-cluster-local/19144 "2025-07-22T12:09:42Z")
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 so… --- ## [Addon DNS - arguments in launch configuration](https://discuss.kubernetes.io/t/addon-dns-arguments-in-launch-configuration/32298)
**Author:** [@Sunshine007](https://discuss.kubernetes.io/u/Sunshine007)\ **Replies:** 0\ **Last updated:** [May 9, 2025, 12:45pm UTC](https://discuss.kubernetes.io/t/addon-dns-arguments-in-launch-configuration/32298 "2025-05-09T12:45:45Z")
Hi - I am still quite new to k8s but really trying to get better. I was working quite strongly now with launch configurations in microk8s and wanted to add the nameservers dns should use as arguments. According to the … --- ## [Coredns Issue on Kubernetes Cluster](https://discuss.kubernetes.io/t/coredns-issue-on-kubernetes-cluster/32179)
**Author:** [@Savita\_Burnwal](https://discuss.kubernetes.io/u/Savita_Burnwal)\ **Replies:** 1\ **Last updated:** [April 23, 2025, 6:39am UTC](https://discuss.kubernetes.io/t/coredns-issue-on-kubernetes-cluster/32179 "2025-04-23T06:39:16Z")
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 C… --- ## [Shorthand of statefulset pod FQDN (quickstart-es-master-0.quickstart-es-master.elastic-system.svc) is not getting resolved](https://discuss.kubernetes.io/t/shorthand-of-statefulset-pod-fqdn-quickstart-es-master-0-quickstart-es-master-elastic-system-svc-is-not-getting-resolved/32099)
**Author:** [@akshay\_verma](https://discuss.kubernetes.io/u/akshay_verma)\ **Replies:** 0\ **Last updated:** [April 9, 2025, 6:05am UTC](https://discuss.kubernetes.io/t/shorthand-of-statefulset-pod-fqdn-quickstart-es-master-0-quickstart-es-master-elastic-system-svc-is-not-getting-resolved/32099 "2025-04-09T06:05:38Z")
Hi Team, I am facing the below issue - FQDN - quickstart-es-master-0.quickstart-es-master.elastic-system.svc - is not getting resolved FQDNS - quickstart-es-master-0.quickstart-es-master.elastic-system.svc.cluster.lo… --- ## [Access MySQL database outside the cluster](https://discuss.kubernetes.io/t/access-mysql-database-outside-the-cluster/31657)
**Author:** [@titanve](https://discuss.kubernetes.io/u/titanve)\ **Replies:** 1\ **Last updated:** [February 24, 2025, 12:50am UTC](https://discuss.kubernetes.io/t/access-mysql-database-outside-the-cluster/31657 "2025-02-24T00:50:00Z")
Cluster information: Kubernetes version: kubectl version Client Version: v1.29.14 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.14 Cloud being used: linode server Installation method: … --- ## [CoreDNS not filter incorrect settings in /etc/resolv.conf](https://discuss.kubernetes.io/t/coredns-not-filter-incorrect-settings-in-etc-resolv-conf/30083)
**Author:** [@yuanyuefeng](https://discuss.kubernetes.io/u/yuanyuefeng)\ **Replies:** 1\ **Last updated:** [October 22, 2024, 1:28am UTC](https://discuss.kubernetes.io/t/coredns-not-filter-incorrect-settings-in-etc-resolv-conf/30083 "2024-10-22T01:28:14Z")
What happened? Recently , eanbled dns cache on host itself where update /etc/resolv.conf files as below : search aaa.bbb.com ccc.com nameserver 127.0.0.1 nameserver A.A.A.A nameserver B.B.B.B options ends0 timeout:3 … --- ## [External domain name resolution is not working inside pods](https://discuss.kubernetes.io/t/external-domain-name-resolution-is-not-working-inside-pods/26609)
**Author:** [@shivam99](https://discuss.kubernetes.io/u/shivam99)\ **Replies:** 4\ **Last updated:** [September 27, 2024, 4:35pm UTC](https://discuss.kubernetes.io/t/external-domain-name-resolution-is-not-working-inside-pods/26609 "2024-09-27T16:35:19Z")
I have setup single node cluster on digital ocean droplet with ingress-nginx (hostNetwork: true). Installation method followed. My ingress service is working i am able to access Next.js using https on it. Internal Networ… --- ## [Could not translate host name "pg" to address: Temporary failure in name resolution](https://discuss.kubernetes.io/t/could-not-translate-host-name-pg-to-address-temporary-failure-in-name-resolution/29776)
**Author:** [@adelkets](https://discuss.kubernetes.io/u/adelkets)\ **Replies:** 5\ **Last updated:** [September 19, 2024, 3:08pm UTC](https://discuss.kubernetes.io/t/could-not-translate-host-name-pg-to-address-temporary-failure-in-name-resolution/29776 "2024-09-19T15:08:28Z")
Hi all. Deploying a Django application to Kubernetes. When I want to perform migrations in a container. An error appears that dns “pg” does not resolve. How can I fix this? /usr/local/lib/python3.9/site-packages/django… --- ## [Trouble Installing My Own CoreDNS in Microk8s](https://discuss.kubernetes.io/t/trouble-installing-my-own-coredns-in-microk8s/29763)
**Author:** [@amc](https://discuss.kubernetes.io/u/amc)\ **Replies:** 0\ **Last updated:** [September 16, 2024, 3:42am UTC](https://discuss.kubernetes.io/t/trouble-installing-my-own-coredns-in-microk8s/29763 "2024-09-16T03:42:17Z")
I am trying to run with the newest Helm chart for CoreDNS. I’m installing Microk8s, disabling the dns addon, then running the standard Helm chart for CoreDNS. As near as I can tell, this should be all I need. And yet, th… --- ## [Accessing service in different namespace](https://discuss.kubernetes.io/t/accessing-service-in-different-namespace/28045)
**Author:** [@chakradarraju](https://discuss.kubernetes.io/u/chakradarraju)\ **Replies:** 0\ **Last updated:** [April 27, 2024, 8:57am UTC](https://discuss.kubernetes.io/t/accessing-service-in-different-namespace/28045 "2024-04-27T08:57:14Z")
Trying to scale a deployment using custom metric from api response, implmenting using keda: I see this error: Normal KEDAScalersStarted 15m keda-operator Started scalers watch Normal ScaledObject… --- ## [Coredns stuck at ContainerCreating and not coming into ready state](https://discuss.kubernetes.io/t/coredns-stuck-at-containercreating-and-not-coming-into-ready-state/24043)
**Author:** [@rkbejawar](https://discuss.kubernetes.io/u/rkbejawar)\ **Replies:** 2\ **Last updated:** [April 20, 2024, 10:35pm UTC](https://discuss.kubernetes.io/t/coredns-stuck-at-containercreating-and-not-coming-into-ready-state/24043 "2024-04-20T22:35:57Z")
Coredns stuck at ContainerCreating and not coming into ready state Cluster information: Kubernetes version: v1.23.7 Cloud being used: (put bare-metal if not on a public cloud) Installation method: Host OS: CentOS Li… --- ## [Coredns resolution between pods not working](https://discuss.kubernetes.io/t/coredns-resolution-between-pods-not-working/27202)
**Author:** [@pietruzzo](https://discuss.kubernetes.io/u/pietruzzo)\ **Replies:** 8\ **Last updated:** [February 27, 2024, 10:01am UTC](https://discuss.kubernetes.io/t/coredns-resolution-between-pods-not-working/27202 "2024-02-27T10:01:50Z")
Hello, I am kinda new to kubernetes and never used coredns before, so apology in advance if any of my question may be dumb. I am running on k3s v1.28.5+k3s1 and coredns-1.29.0 installed using helm. I am just trying to … --- ## [How to whitelist domain in Kubernetes pod using Coredns ACL plugin](https://discuss.kubernetes.io/t/how-to-whitelist-domain-in-kubernetes-pod-using-coredns-acl-plugin/16598)
**Author:** [@Shreya\_Bhatnagar](https://discuss.kubernetes.io/u/Shreya_Bhatnagar)\ **Replies:** 2\ **Last updated:** [January 30, 2024, 4:25pm UTC](https://discuss.kubernetes.io/t/how-to-whitelist-domain-in-kubernetes-pod-using-coredns-acl-plugin/16598 "2024-01-30T16:25:13Z")
How can I use use coredns acl plugin for the domain based access \[blocking/allowing\] the egress calls ? As per my use case I want to control the outgoing calls from my pod. something like this : . { acl { … --- ## [Coredns stuck in "ContainerCreating"](https://discuss.kubernetes.io/t/coredns-stuck-in-containercreating/19100)
**Author:** [@lovesharepc](https://discuss.kubernetes.io/u/lovesharepc)\ **Replies:** 2\ **Last updated:** [January 24, 2024, 1:25pm UTC](https://discuss.kubernetes.io/t/coredns-stuck-in-containercreating/19100 "2024-01-24T13:25:04Z")
I try use kube-vip to create k8s cluster after create CNI ,coredns staus still in ““ContainerCreating”” \[root@k8s-1 ~\]# kubectl get pods -A NAMESPACE NAME READY STATUS … --- ## [Rollback from k8s 1.27.1 to 1.26.3 fails](https://discuss.kubernetes.io/t/rollback-from-k8s-1-27-1-to-1-26-3-fails/24623)
**Author:** [@Kiran\_Katabathena](https://discuss.kubernetes.io/u/Kiran_Katabathena)\ **Replies:** 2\ **Last updated:** [January 22, 2024, 3:29pm UTC](https://discuss.kubernetes.io/t/rollback-from-k8s-1-27-1-to-1-26-3-fails/24623 "2024-01-22T15:29:45Z")
Hi we have k8s 1.27.1 with coredns compatible version 1.10.0 and k8s 1.26.3 with compatible version of 1.9.3. When we upgrade our cluster 1.26.3 =\> 1.27.1 it was fine. When we rollback from 1.27.1 =\> 1.26.3 we have belo… --- ## [Coredns fails connecting to kube-api via kubernetes service](https://discuss.kubernetes.io/t/coredns-fails-connecting-to-kube-api-via-kubernetes-service/25288)
**Author:** [@azzid](https://discuss.kubernetes.io/u/azzid)\ **Replies:** 3\ **Last updated:** [September 14, 2023, 12:27pm UTC](https://discuss.kubernetes.io/t/coredns-fails-connecting-to-kube-api-via-kubernetes-service/25288 "2023-09-14T12:27:11Z")
Cluster information: Kubernetes version: v1.28.1 Cloud being used: bare-metal Installation method: kubeadm Host OS: Ubuntu 22.04.3 LTS CNI and version: cilium 1.14.1 CRI and version: containerd 1.6.22 Today, after … --- ## [CoreDNS \[ERROR\] plugin/errors: 2](https://discuss.kubernetes.io/t/coredns-error-plugin-errors-2/16106)
**Author:** [@letran3691](https://discuss.kubernetes.io/u/letran3691)\ **Replies:** 12\ **Last updated:** [August 17, 2023, 3:12am UTC](https://discuss.kubernetes.io/t/coredns-error-plugin-errors-2/16106 "2023-08-17T03:12:47Z")
Hello everyone Kubernetes version:v1.21.1 Cloud being used: LAB Private Installation method: repo install Host OS: centos7 CNI: flannel I’ve setup a LAB cluster with 3 node (node1, node2, node3), node 1 is master. … --- ## [Dns not resolving \*.svc.cluster.local only \*.svc](https://discuss.kubernetes.io/t/dns-not-resolving-svc-cluster-local-only-svc/24999)
**Author:** [@boina](https://discuss.kubernetes.io/u/boina)\ **Replies:** 0\ **Last updated:** [August 2, 2023, 6:53pm UTC](https://discuss.kubernetes.io/t/dns-not-resolving-svc-cluster-local-only-svc/24999 "2023-08-02T18:53:17Z")
Cluster information: Kubernetes version: v1.27.4 Cloud being used: bare-metal Installation method: kubeadm Host OS: rocky8 CNI and version: v1.1.1 CRI and version: containerd.io-1.6.22 hello everyone i updated my … --- ## [Coredns pods are schedule on cordon node](https://discuss.kubernetes.io/t/coredns-pods-are-schedule-on-cordon-node/24987)
**Author:** [@david-nano](https://discuss.kubernetes.io/u/david-nano)\ **Replies:** 2\ **Last updated:** [August 2, 2023, 1:11pm UTC](https://discuss.kubernetes.io/t/coredns-pods-are-schedule-on-cordon-node/24987 "2023-08-02T13:11:39Z")
Cluster information: Kubernetes version: v1.25.9 Cloud being used: bare-metal Installation method: RKE 1 Host OS: Ubuntu 18.04-20.04 CNI and version: Calico docker.io/calico/node:v3.23.1 docker.io/calico/cni:v3.23.… --- ## [Enabling DNSSEC on the cluster level](https://discuss.kubernetes.io/t/enabling-dnssec-on-the-cluster-level/24295)
**Author:** [@psst\_um\_lakia](https://discuss.kubernetes.io/u/psst_um_lakia)\ **Replies:** 0\ **Last updated:** [May 23, 2023, 2:45am UTC](https://discuss.kubernetes.io/t/enabling-dnssec-on-the-cluster-level/24295 "2023-05-23T02:45:39Z")
Cluster information: Kubernetes version: v1.27.1 Cloud being used: bare-metal Host OS: Ubuntu 20 CNI and version: calico v3.25.1 CRI and version: containerd://1.6.12z I am trying to enable DNSSEC for the cluster ser… --- ## [Kubernetes NGINX Ingress redirecting POST requests to GET](https://discuss.kubernetes.io/t/kubernetes-nginx-ingress-redirecting-post-requests-to-get/24263)
**Author:** [@adicop49](https://discuss.kubernetes.io/u/adicop49)\ **Replies:** 0\ **Last updated:** [May 20, 2023, 2:14pm UTC](https://discuss.kubernetes.io/t/kubernetes-nginx-ingress-redirecting-post-requests-to-get/24263 "2023-05-20T14:14:30Z")
I am facing issue when trying to POST request in POSTMAN. Below is the question I posted in stackoverflow. please help me to resolve --- ## [CoreDns is running but not ready](https://discuss.kubernetes.io/t/coredns-is-running-but-not-ready/17671)
**Author:** [@utshab500](https://discuss.kubernetes.io/u/utshab500)\ **Replies:** 1\ **Last updated:** [February 2, 2023, 9:24am UTC](https://discuss.kubernetes.io/t/coredns-is-running-but-not-ready/17671 "2023-02-02T09:24:18Z")
Hey everyone, I have run into an interesting issue which is me and my team were trying to setup bare-metal K8 cluster. We got one cluster perfectly running then we went for the next one. There We found the DNS is not bei… --- ## [Kubeadm init error: addon/coredns unable to create serviceaccount!](https://discuss.kubernetes.io/t/kubeadm-init-error-addon-coredns-unable-to-create-serviceaccount/21981)
**Author:** [@slevin](https://discuss.kubernetes.io/u/slevin)\ **Replies:** 0\ **Last updated:** [November 17, 2022, 7:57pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-error-addon-coredns-unable-to-create-serviceaccount/21981 "2022-11-17T19:57:49Z")
Hello all, I’m stuck with an issue that I’m not able to understand and to get the origin, After being installing all required tools and trying many times the creation of a cluster using kubeadm, an error is raised -at … --- ## [Nodelocal DNS Cache can not resolve /etc/hosts each node](https://discuss.kubernetes.io/t/nodelocal-dns-cache-can-not-resolve-etc-hosts-each-node/21233)
**Author:** [@marco210](https://discuss.kubernetes.io/u/marco210)\ **Replies:** 0\ **Last updated:** [September 9, 2022, 7:53am UTC](https://discuss.kubernetes.io/t/nodelocal-dns-cache-can-not-resolve-etc-hosts-each-node/21233 "2022-09-09T07:53:08Z")
Asking for help? Comment out what you need so we can get more information to help you! Each /etc/hosts node have local domain xx.xx.xx.xx harbor.io. Before install Nodelocal DNS Cache, in another pod I can dig harbor.io … --- ## [Coredns is in CrashLoopBackOff state with "no nameservers found" error log](https://discuss.kubernetes.io/t/coredns-is-in-crashloopbackoff-state-with-no-nameservers-found-error-log/17863)
**Author:** [@Daigo](https://discuss.kubernetes.io/u/Daigo)\ **Replies:** 2\ **Last updated:** [August 10, 2022, 11:32pm UTC](https://discuss.kubernetes.io/t/coredns-is-in-crashloopbackoff-state-with-no-nameservers-found-error-log/17863 "2022-08-10T23:32:10Z")
I have tried to build kubernetes using kubeadm on my bare-metal server, but it seemed that coredns failed to start after installing cni (weave-net). Two coredns containerd are now in “CrashLoopBackOff” state, and the lo… --- ## [coreDNS returning IP instead of hostname for redirect\_url](https://discuss.kubernetes.io/t/coredns-returning-ip-instead-of-hostname-for-redirect-url/20099)
**Author:** [@Mark\_Templeton](https://discuss.kubernetes.io/u/Mark_Templeton)\ **Replies:** 0\ **Last updated:** [May 20, 2022, 4:47pm UTC](https://discuss.kubernetes.io/t/coredns-returning-ip-instead-of-hostname-for-redirect-url/20099 "2022-05-20T16:47:26Z")
Cluster information: Kubernetes version: v1.19.7 I have a custom entry for hostnames in coreDNS and this works fine for resolving the hostnames. hosts custom.hosts example.com { 1.1.1.1 server1.example.co… [Next page](https://discuss.kubernetes.io/tag/coredns/37.md?match_all_tags=true&page=1&tags%5B%5D=coredns)