After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 682995 - Global DNS settings.
Global DNS settings.
Status: RESOLVED DUPLICATE of bug 690404
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Pavel Simerda
NetworkManager maintainer(s)
Depends on:
Blocks: nm-1.0 695213
 
 
Reported: 2012-08-29 21:24 UTC by Daniel Leining
Modified: 2013-03-05 15:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Leining 2012-08-29 21:24:50 UTC 
NetworkManager should have a global setting for dns servers. It's really annoying having to set induvidual settings for each connection, or have to lock /etc/resolv.conf to keep the servers I want. A bit too hacky for my taste.
Comment 1 Pavel Simerda 2012-08-31 14:54:52 UTC 
I think a global DNS for NetworkManager doesn't make sense. It's a very advanced
usage of networking and could be satisfied by just adding an option that would
cause NetworkManager to *ignore* /etc/resolv.conf and not to rewrite it.

Is this acceptable for you?
Comment 2 maratbn 2012-09-01 22:40:27 UTC 
Just to chime in, I think it would be great if there was a configuration setting to prevent NetworkManager from overwriting '/etc/resolv.conf'.
Comment 3 Pavel Simerda 2012-11-01 11:19:33 UTC 
I am going to make usage of resolv.conf optional (enabled by default). Direct
edit is just one of three ways NM can currently modify resolv.conf. The other
are the resolvconf program and SUSE's netconfig program.
Comment 4 Pavel Simerda 2013-03-05 15:05:54 UTC 

*** This bug has been marked as a duplicate of bug 690404 ***