# Howto teach my awx minikube cluster about my internal DNS resolvers at deployment time?

**URL:** <https://forum.ansible.com/t/howto-teach-my-awx-minikube-cluster-about-my-internal-dns-resolvers-at-deployment-time/36721>\
**Category:** AWX Project\
**Tags:** windows, awx, kubernetes\
**Created:** [June 13, 2022, 10:18am UTC](https://forum.ansible.com/t/howto-teach-my-awx-minikube-cluster-about-my-internal-dns-resolvers-at-deployment-time/36721 "2022-06-13T10:18:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Urs\_Rau](https://avatars.discourse-cdn.com/v4/letter/u/50afbb/32.png) [@Urs\_Rau](https://forum.ansible.com/u/Urs_Rau)\
**Post date:** [June 13, 2022, 10:18am UTC](https://forum.ansible.com/t/howto-teach-my-awx-minikube-cluster-about-my-internal-dns-resolvers-at-deployment-time/36721/1 "2022-06-13T10:18:42Z")

</div>

I am using the new operator (v 0.22.0) method to deploy awx 21.1.0 into a test minikuke Kubernetes cluster using the basic install as documented in

[https://github.com/ansible/awx-operator#basic-install](https://github.com/ansible/awx-operator#basic-install)

How or where to I set my awx related pods to know to use my internal dns resolvers to find my local linux and windows machines?  
Both winrm and kerberos totally depend on a fully working DNS, fr linux I could get away by setting the IP under the ansible\_host var, but in my test setup the awx pods do not know about my internal zone dns servers and active directory domain controllers.

How do I set this so the operator deploy injects that info into all its pods in the awx namespace?

Thanks for any help or pointers. I can go and edit ephemeral pods and manually inject the info into the /etc/resov.conf, but in Kubernetes deployment that just feels wrong.

---

<div class="post-metadata">

**Author:** ![Urs\_Rau](https://avatars.discourse-cdn.com/v4/letter/u/50afbb/32.png) [@Urs\_Rau](https://forum.ansible.com/u/Urs_Rau)\
**Post date:** [June 13, 2022, 10:51am UTC](https://forum.ansible.com/t/howto-teach-my-awx-minikube-cluster-about-my-internal-dns-resolvers-at-deployment-time/36721/2 "2022-06-13T10:51:35Z")

</div>

Replying to one’s own question is a either a sign of oncoming madness or alternatively might be a sign that one wants to share what has been found  
( and also making sure in the process that next time around the answer can be found when searching with google. 😉 )

I found this article here helpful:

[http://pwittrock.github.io/docs/tasks/administer-cluster/dns-custom-nameservers/](http://pwittrock.github.io/docs/tasks/administer-cluster/dns-custom-nameservers/)

So in my case I put the following in a yaml file and then applied it with ‘kubectl apply -f my-local-dns.yml’

apiVersion: v1  
kind: ConfigMap  
metadata:  
name: kube-dns  
namespace: kube-system  
data:  
stubDomains: |  
{“example.dom”: [“10.100.150.100”, “10.100.150.200”]}  
upstreamNameservers: |  
[“1.0.0.2”, “1.1.1.2”]

HTH somebody else too. After this I could resolve and info my local zone hosts on the awx task and ee and web containers.

PS:  
Sorry for this ‘duplicate’ post. I had not immediately realised that there is a awx-project google group and posted off topic to ansible-project google group first instead.