Bug 458822 - Network Manager does not save custom DNS settings
Network Manager does not save custom DNS settings
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-08-12 10:28 EDT by markm
Modified: 2008-11-02 17:20 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-02 17:20:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description markm 2008-08-12 10:28:16 EDT
Description of problem:

Network manager does not save custom DNS settings - just drops them without any warning.

Version-Release number of selected component (if applicable):

NetworkManager Applet 0.7.0

How reproducible:


Steps to Reproduce:
1. open an existing wireless connection / create a new connection
2. on the IPv4 Settings page do:
 * Method: Manual or Automatic with manual DNS settings
 * Addresses: Address: Prefix: 24 Gateway:
 * DNS Servers:,
3. Press 'OK' button
4. Select your connection and click “edit” button on the side
Actual results:

everything is set as request but DNS Servers, field remains empty

Expected results:

Network Manager remembers manual DNS settings

Additional info:

It used to work, I've set up another connection couple of months ago and it remembered manual DNS Settings, this time it does not work, even after a computer restart. It is a really bad user experience - I just flew in to Spain and wanted to use internet, Network Manager does not allow me to do so - I had to write a simple cron job which overwrites /etc/resolv.conf every couple of minutes with correct DNS settings.
Comment 1 Dan Williams 2008-11-02 17:20:52 EST
Should be fixed in latest updates (svn4022 and later).

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