Bug 1046701 - [network] gnome-control-center should allow editing DNS search list in Fedora 20
Summary: [network] gnome-control-center should allow editing DNS search list in Fedora 20
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-26 16:25 UTC by Jonathan Kamens
Modified: 2016-09-24 14:33 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-24 14:33:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 771918 0 None None None 2016-09-24 14:33:12 UTC

Description Jonathan Kamens 2013-12-26 16:25:00 UTC
In Fedora 19 I was able to edit the list of domains that I want my laptop to search when connected to each WiFi or wired network.

This setting appears to have vanished in Fedora 20 -- I can't find anywhere to edit it in the NetworkManager applet. The setting still _exists_, because I see that a value for it that I put in when my laptop was running Fedora 19 is still in effect, but I've no way to modify it.

Comment 1 Bill Gianopoulos 2013-12-27 13:13:17 UTC
Same issue here.

There does not appear to be any methodology to get the search or domain entries added into /etc/resolv.conf unless you are using dhcp.

Of course you can add it manually, but that disappears on the next reboot.

The only way around this appears to be to manually add DOMAIN= entry to the ifcfg-<ifname> file in /etc/sysconfig/network-scripts corresponding to the appropriate interface.

Comment 2 Samuel Sieb 2013-12-27 18:55:01 UTC
I'm still using F19 and there is no way to edit the DNS domain search from the Network Settings dialog from the network menu.  The only way to edit it is from the NM network connection manager application.

Comment 3 Bill Gianopoulos 2013-12-27 21:15:00 UTC
IN firefox20 there does not seem to be anyway to do it other than hand editing the file.  If someone knows of a way to actually do this via a configuration GUI, please post it here and update the release notes to include such documentation.

Comment 4 Samuel Sieb 2013-12-27 21:31:26 UTC
yum install nm-connection-editor

Comment 5 Bill Gianopoulos 2013-12-27 23:07:17 UTC
Well if that actually fixes this that is a huge issue.  This is kind of my entire issue with recent fedora releases.  If I wanted to run a dumbed down thing where you can not customize it the way you want, fedora would never have been my distribution of choice.  Making it be a distribution for not techies is not the right path to making it more accepted.

Comment 6 Fabian Deutsch 2014-01-17 07:49:44 UTC
What about adding a "Advanced" button to the default NM dialog/applet thingy, which either opens the nm-connection-editor or - if the "Advanced" button is per-connection - open the nm-connection-editor dialog for that specific connection.

Comment 7 Jirka Klimes 2014-02-21 11:44:36 UTC
The issue is that people make vague statements that something doesn't work on Fedora 20. But they should be more specific and say what components, tools they are using, what versions, etc. Else it is difficult to find what is really the problem and also the report won't go to right people.

So in this case I guess the problem is that "Network" module of gnome-control-center doesn't offer DNS searches to be edited. So I am reassigning the bug to control-center component.

A workaround is to use nm-connection-editor as suggested.

Comment 8 Fedora End Of Life 2015-05-29 10:10:44 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Jonathan Kamens 2015-05-29 12:40:28 UTC
Still can't edit domain search list in control center in Fedora 22.

Comment 10 Fedora End Of Life 2016-07-19 10:50:04 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 11 Jan Kurik 2016-07-26 04:09:54 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 12 Bastien Nocera 2016-09-24 14:33:13 UTC
I've moved this RFE upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=771918

If the commenters and original reporter here could explain the use case behind their use of DNS search lists[1] in the upstream bug, that would be most welcome, as we need to figure out whether we want to add the functionality.

[1]: Explanations of the network setups where you use this functionality, why it cannot be setup through the DHCP server, etc.


Note You need to log in before you can comment on or make changes to this bug.