[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: When should dnsmasq be disabled?


Always read the latest documentation unless you're still on verision 3.2.


As of OpenShift Origin 1.2, dnsmasq is automatically configured on all masters and nodes. The pods use the nodes as their DNS, and the nodes forward the requests. By default, dnsmasq is configured on the nodes to listen on port 53, therefore the nodes cannot run any other type of DNS application.

I think you should disable dnsmasq if you don't use network manager but then you will run into issues as dnsmasq and DNS setup scripts are part of OpenShift configuration so you're better off to keep it like that. Just make sure you have no other DNS running. I cannot at the moment predict any situation when you should disable dnsmasq in the cluster. 


On 16 August 2017 at 11:12, Yu Wei <yu2003w hotmail com> wrote:


I setup openshift origin cluster with dnsmasq enabled.

I found that within cluster dns didn't function correctly.

For example, within pod, "nameserver" was not added in /etc/resolv.conf.

And service names, endpoints couldn't be resolved.

After setting openshift_use_dnsmasq = false and reinstalled cluster, it seemed that dns started to work.

Why should openshift_use_dnsmasq be set to false?

I also read the documentation in below link.


I'm still not quite understand when dnsmasq should be disabled.

"for example, if your /etc/resolv.conf is managed by a configuration tool other than NetworkManager".

I setup openshift origin cluster on VMs provisioned by openstack.

For my environments, should I disable dnsmasq? Or did I make any improper configurations?


Jared, (韦煜)
Software developer
Interested in open source software, big data, Linux

users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]