-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu 16.04 and dnsmasq #72
Comments
Hi Thank you for the info, I'll update the Readme about this. Regards |
Thanks for the reply :) Just checked, Ubuntu 14.04 uses dnsmasq as well. On the other hand, turns out it's not a replacement for editing /etc/resolv.conf inside the docker containers running ubuntu |
And thanks for taking care of the project 👍 |
You're welcome Running Ubuntu in containers is not recommended. Systemd has issues with this. For dnsdock I recommend using the rockerfile based on alpine. |
While trying to set up dnsdock on ubuntu 16.04 i discovered that 16.04 has default system configured in such a way that network manager is using dnsmasq running on local ip address (in my case it's 127.0.1.1 and port 53).
While editing the /etc/resolv.conf works until the machine restarts (or config is overwritten by any other means), i found that one can also configure dnsmasq to use the dnsdock only for
.docker
domains by creating a file/etc/NetworkManager/dnsmasq.d/local-docker.conf
withwhile running dnsdock as
dnsdock -dns="172.17.0.1:53"
(since 127.0.1.1:53 is taken by dnsmasq).The difference is that the DNS for non-docker domains remains under the NetworkManager's control and there will be no need to amend /etc/resolv.conf on every restart. Whether that is a pro or a con, it's up to you :)
The text was updated successfully, but these errors were encountered: