# NXDomain DNS errors with latest minikube and headless K8s service

**URL:** <https://discuss.kubernetes.io/t/nxdomain-dns-errors-with-latest-minikube-and-headless-k8s-service/2998>\
**Category:** General Discussions\
**Tags:** minikube, coredns\
**Created:** [October 3, 2018, 12:44pm UTC](https://discuss.kubernetes.io/t/nxdomain-dns-errors-with-latest-minikube-and-headless-k8s-service/2998 "2018-10-03T12:44:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![franck102](https://avatars.discourse-cdn.com/v4/letter/f/35a633/32.png) [@franck102](https://discuss.kubernetes.io/u/franck102)\
**Post date:** [October 3, 2018, 12:44pm UTC](https://discuss.kubernetes.io/t/nxdomain-dns-errors-with-latest-minikube-and-headless-k8s-service/2998/1 "2018-10-03T12:44:41Z")

</div>

Hi all,

After upgrading to Minikube v0.29.0 I am seeing a new DNS issue with an existing cluster: in summary, with a single external service named “mysql”, and a single pod trying to consume the service, I am getting DNS resolution errors from CoreDNS (see details below).  
I have seen the issue mentioned here: [https://github.com/coredns/coredns/issues/1365](https://github.com/coredns/coredns/issues/1365)  
… but that doesn’t offer any good workaround.

Is it possible to configure minikube to revert to using kube-dns for now to work around this? Any other suggestion?

Any help appreciated… thanks!  
Franck

\*\* Edit: as far as reverting to kube-dns goes, I should have googled first:

> minikube addons disable coredns  
> minikube enable kube-dns  
> … does the trick.

Here are the details about the system:

Host OS: OS X Darwin  
VirtualBox 5.2.18  
minikube version: v0.29.0

## minikube config view

- vm-driver: virtualbox
- cpus: 4
- heapster: true
- ingress: true
- memory: 8000

## mysql service:

{  
“kind”: “Service”,  
“apiVersion”: “v1”,  
“metadata”: {  
“name”: “mysql”,  
“namespace”: “dmpdev”,  
“selfLink”: “/api/v1/namespaces/dmpdev/services/mysql”,  
“uid”: “931e8a80-c6f0-11e8-a2c7-080027c10094”,  
“resourceVersion”: “5813”,  
“creationTimestamp”: “2018-10-03T09:41:59Z”  
},  
“spec”: {  
“type”: “ExternalName”,  
“sessionAffinity”: “None”,  
“externalName”: “192.168.1.19”  
},  
“status”: {  
“loadBalancer”: {}  
}  
}

**## kc logs --namespace kube-system coredns-c4cffd6dc-68lnv**

> 172.17.0.2:58109 - [03/Oct/2018:12:38:31 +0000] 27832 “AAAA IN mysql. udp 23 false 512” NXDOMAIN qr,rd,ra 99 0.000219445s
> 
> 172.17.0.2:58109 - [03/Oct/2018:12:38:31 +0000] 39231 “A IN mysql. udp 23 false 512” NXDOMAIN qr,rd,ra 99 0.00016881s  
> 172.17.0.2:33761 - [03/Oct/2018:12:38:35 +0000] 11544 “A IN mysql.cluster.local. udp 37 false 512” NXDOMAIN qr,aa,rd,ra 130 0.000094423s
> 
> 172.17.0.2:33761 - [03/Oct/2018:12:38:35 +0000] 52542 “AAAA IN mysql.cluster.local. udp 37 false 512” NXDOMAIN qr,aa,rd,ra 130 0.00007489s
> 
> 172.17.0.2:55709 - [03/Oct/2018:12:38:39 +0000] 62827 “AAAA IN mysql.dmpdev.svc.cluster.local. udp 48 false 512” NXDOMAIN qr,rd,ra 141 0.000110013s
> 
> 172.17.0.2:55709 - [03/Oct/2018:12:38:39 +0000] 18219 “A IN mysql.dmpdev.svc.cluster.local. udp 48 false 512” NXDOMAIN qr,rd,ra 141 0.000208986s