I did not install anything that would have set up dnsmasq. I did a fresh install of the latest RHEL 7.2 a few weeks ago. I installed the "server with GUI". I installed Docker, pulled down the latest Openshift Binary and started that. I did a little research myself. Apparently dnsmasq is part of the standard Network Manager responsible for detecting and configuring my network cards to access the internet.
On Thu, Feb 11, 2016 at 8:59 AM, Scott Dodson <[email protected]> wrote: > Specifically, alter your master config so it binds to a different > port. In /etc/origin/master/master-config.yaml > > dnsConfig: > bindAddress: 0.0.0.0:8053 > bindNetwork: tcp4 > > I'm curious though, do you not remember setting up dnsmasq on this > host? I'm working on changes to dns implementation for 1.2/3.2 and I'd > like to understand if something has automatically configured dnsmasq > for you. > > On Fri, Jan 29, 2016 at 12:16 AM, Dean Peterson <[email protected]> > wrote: > > Oh boy, well thank you for the information. I looked at my old machine > > running openshift origin 1.0.7 and it has dnsmasq running on port 53 and > > things seem to work fine. External traffic routes to my containers > running > > in openshift. Also, I did have my setup running on this new machine for > a > > couple of days and things with dnsmasq running on 53 seemed to work > too. Is > > giving port 53 over to openshift really necessary? > > > > On Thu, Jan 28, 2016 at 10:28 PM, Michael Surbey <[email protected]> > wrote: > >> > >> Port 53 is reserved for the Domain Name System (DNS). > >> > >> In your case it is the DNS cacher "/usr/sbin/dnsmasq" of the package > >> dnsmasq-base that's causing this error message. > >> > >> This pre-installed package is a dependency of network-manager, the > >> Network Manager of your desktop environment (e.g. Unity, GNOME, …). > >> > >> If you'd like to keep NetworkManager alive, you can create a custom DNS > >> in order to move the SkyDNS server to a different port (i.e. 8053) and > >> have the dnsmasq server forward local requests to it by installing > >> dnsmasq (fully) and following these guides: > >> > >> - http://red.ht/1Im8qLI > >> - http://bit.ly/1J5FCHf > >> > >> Otherwise, consider the following comments - http://bit.ly/23x4NK2 - > >> before attempting to remove dnsmasq-base or kill port 53. > >> > >> Sincerely, > >> > >> Mike > >> On 01/28/2016 10:03 PM, Dean Peterson wrote: > >> > I installed RHEL 7.2 from scratch, then installed Docker and > downloaded > >> > and > >> > started Openshift 1.1.1. I had been having trouble getting this > version > >> > to > >> > run reliably. I noticed just recently on startup it was complaining > >> > about > >> > port 53 already being bound. I saw that dnsmasq was using the port. > I > >> > killed dnsmasq and restarted openshift. Now when I look to see what > is > >> > using port 53; openshift is (as I would expect). I am wondering; does > >> > RHEL > >> > 7.2 start dnsmasq or does installing the latest version of docker > >> > available > >> > to RHEL start it? It seems, Openshift being closely linked to RHEL, > >> > this > >> > should be known and mentioned prominently - dnsmasq should be stopped > >> > before starting Openshift. > >> > > >> > > >> > > >> > _______________________________________________ > >> > users mailing list > >> > [email protected] > >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >> > > > > > > > > > _______________________________________________ > > users mailing list > > [email protected] > > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
