GNOME Bugzilla – Bug 705962
Network Manager should allow setting global DNS servers
Last modified: 2013-08-14 10:21:52 UTC
As more and more internet service providers and institutions use DNS to sensor internet, being able to use a DNS provider without sensorship is becoming all the more important for everyone. There should be an option to use a particular DNS server across all connections, if there is an easy option to use Open NIC project, it would be even more awesome. Currently it allows only setting per connection DNS, and that also is broken as manually set DNS is only added as second choice when it should be the first choice.
(In reply to comment #0) > As more and more internet service providers and institutions use DNS to sensor > internet, being able to use a DNS provider without sensorship is becoming all > the more important for everyone. This is currently being done by setting the DNS servers for the connection that is being used for default routing. It has a good reason as not all connections let you use foreign DNS servers. Therefore if you want to get it right, it's a rather complicated task. I believe that the task is more suitable for RDNSS servers like unbound or dnsmasq, magical configurators like dnssec-trigger and/or NetworkManager dispatcher scripts. You can already disable NetworkManager's resolv.conf management by globally setting dns=none, set up a local RDNSS and delete /etc/resolv.conf (or write 'nameserver 127.0.0.1' there). I'm marking this ticket WONTFIX because of the above. Feel free to contact other developers or provide more information. > There should be an option to use a particular > DNS server across all connections, if there is an easy option to use Open NIC > project, it would be even more awesome. OpenNIC project would also be much easier to via [a tool similar to] dnssec-trigger as those handle all sorts of magic like tunneling the DNS traffic if the classic DNS port is blocked and/or letting the user turn the feature on/off. > Currently it allows only setting per connection DNS, And turning off resolv.conf management via global dns=none, configuring your own local RDNSS and setting up a dispatcher script for whatever settings you want to convey from NetworkManager to your RDNSS (like local DHCP/VPN zones/nameservers). An example of such a script was AFAIK added recently to upstream dnssec-trigger. See also: https://open.nlnetlabs.nl/pipermail/dnssec-trigger/2013-July/000210.html (adding thozza to this bug report dispite closing it) Feel free to reach me via mail or IRC for more details or add more comments under the closed bug report. https://fedoraproject.org/wiki/User:Pavlix > and that also is broken Please be more specific. Describe a configuration of DNS for a single connection that you wish to use, the expected result and the actual result in detail. If it doesn't work, it might be preferable to start a new bug report for that. > as > manually set DNS is only added as second choice when it should be the first > choice. I don't understand (1) what do you mean by first/second choice nor (2) why should order make something broken.