You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 with
server=/docker/172.17.0.1
while 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:
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: