Public bug reported:
The only mention of dnsmasq in the manpage only refers to resolver.conf. This
is misleading
since dns=none would appear to stop NetworkManager from running dnsmasq, yet it
does not. So
until the non-existent "disable dnsmasq" checkbox/radio button appears in the
NetworkManager gui interface (edit connections) the documentation MUST include
narrative on proper way to use NetworkManager with dhcpd, bind9 and friends.
The amount of confusion and wasted time caused by this can easily be seen on
google. After three days of work I am still uncertain that its even possible.
This applies to 16.04 specificly but has been an issue since
NetworkManager started using dnsmasq.
>From the manpage:
man NetworkManager.conf
dns
Set the DNS (resolv.conf) processing mode.
default: The default if the key is not specified.
NetworkManager will update resolv.conf to reflect the nameservers
provided by currently active connections.
dnsmasq: NetworkManager will run dnsmasq as a local caching
nameserver, using a "split DNS" configuration if you are connected to a VPN,
and then update resolv.conf to point to the
local nameserver.
unbound: NetworkManager will talk to unbound and dnssec-triggerd,
providing a "split DNS" configuration with DNSSEC support. The /etc/resolv.conf
will be managed by dnssec-trigger
daemon.
none: NetworkManager will not modify resolv.conf.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648164
Title:
NetworkManager documentation does not document proper way to use
different tools for dns /dhcp management
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1648164/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
