Bug 221426

Summary:	global DNS server setting
Product:	[Unmaintained] knetworkmanager	Reporter:	Beat Wolf <asraniel>
Component:	general	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED UPSTREAM
Severity:	wishlist	CC:	4wy78uwh, gobbledegeek, lamarque
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Beat Wolf 2010-01-05 18:17:17 UTC

Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

It would be really nice to have a easy setting to change the DNS server, perhaps even globaly. Today with net censorship, surveilance etc, a global DNS setting would be nice, perhaps already populated (not activated) with a few free DNS servers like opendns or google.

I had this idea because recently the DNS servers of my ISP went down for several hours, and for the average user it was impossible to go back online.

So the way i would imagine it is the following way:
Easy UI to add a list of free DNS servers, populated by a few basic ones as a starter if you don't have a working DNS server.
option to always use those DNS servers
option to define per connection if the global DNS server setting is used.

if the network manager detects that the DNS server is down, propose to use the global DNS settings as a fix (very usefull for the average user). I think that the DNS server is down is already detected, at least knetwork manager had a little symbol that something is wrong with my connection (and that something was a non working DNS server).

Comment 1 gobbledegeek@gmail.com 2010-05-17 08:15:03 UTC

I would suggest this not be made an auto-default, rather it require manual activation because this will cause poor performance with CDNs that use the geo-location of your DNS IP to route you to a nearby server. Hence a manual activation will make the end-user more aware why he is having "performance problems" with certain websites.

Comment 2 Lamarque V. Souza 2011-05-27 06:56:45 UTC

This should be done in NM daemon, not in the clients like Plasma NM.

Comment 3 Lamarque V. Souza 2011-07-12 04:53:06 UTC

Since Plasma NM run as non-root user it cannot change DNS settings without proper NM support. You should report this request to NM first, when it support it then we can implement it in Plasma.

Comment 4 Roke Julian Lockhart Beedell 2022-05-19 00:30:16 UTC

Has this been reported as was suggested?