| 2007-03-13 10:55:02 |
StaticFish |
bug |
|
|
added bug |
| 2007-09-01 17:32:42 |
Henrik Nilsen Omma |
network-manager: importance |
Undecided |
Low |
|
| 2007-09-01 17:32:42 |
Henrik Nilsen Omma |
network-manager: status |
New |
Incomplete |
|
| 2008-04-15 08:38:00 |
Adam Niedling |
network-manager: status |
Incomplete |
New |
|
| 2008-04-16 15:33:25 |
Matt Sicker |
network-manager: status |
New |
Confirmed |
|
| 2008-10-27 12:48:05 |
Alexander Sack |
network-manager: status |
Confirmed |
Fix Released |
|
| 2008-10-27 12:48:05 |
Alexander Sack |
network-manager: statusexplanation |
Enough people here (including myself) can confirm this issue, and despite having an interesting workaround, this is a UI issue that should be looked into. |
this is fixed in intrepid in various ways: a) resolvconf works, b) NM now supports setting dns details manually, etc. |
|
| 2008-11-16 01:53:45 |
Djihed |
network-manager: status |
Fix Released |
New |
|
| 2008-11-16 01:53:45 |
Djihed |
network-manager: statusexplanation |
this is fixed in intrepid in various ways: a) resolvconf works, b) NM now supports setting dns details manually, etc. |
I meant the opendns workaround.
I am afraid this bug is still unfixed for Intrepid.
Newly installed Intrepid:
Edit connections->IPv4 settings->Automatic address only->I put my DNS servers.
DNS servers are reverted to old settings on next boot. So no, even though NM allows you to set the DNS servers, it doesn't obey them. |
|
| 2008-11-29 23:00:40 |
mati |
network-manager: status |
New |
Confirmed |
|
| 2008-11-29 23:00:40 |
mati |
network-manager: statusexplanation |
I meant the opendns workaround.
I am afraid this bug is still unfixed for Intrepid.
Newly installed Intrepid:
Edit connections->IPv4 settings->Automatic address only->I put my DNS servers.
DNS servers are reverted to old settings on next boot. So no, even though NM allows you to set the DNS servers, it doesn't obey them. |
Confirmed again. Today I've installed Intrepid on another machine. Had to enter DNS settings for my wired connection manually (in XP it is unnecessary - I don't know what is with that connection). I opened NM, set DHCP with custom-set DNS in the IPv4 tab and everything was fine until reboot. Connection was reset to pure DHCP, DNS settings were lost. |
|
| 2008-12-28 14:21:40 |
Alexander Sack |
network-manager: status |
Confirmed |
Triaged |
|
| 2008-12-28 14:21:40 |
Alexander Sack |
network-manager: statusexplanation |
Confirmed again. Today I've installed Intrepid on another machine. Had to enter DNS settings for my wired connection manually (in XP it is unnecessary - I don't know what is with that connection). I opened NM, set DHCP with custom-set DNS in the IPv4 tab and everything was fine until reboot. Connection was reset to pure DHCP, DNS settings were lost. |
dupe of bug 284298 |
|
| 2008-12-28 14:23:05 |
Alexander Sack |
network-manager: status |
Triaged |
Fix Released |
|
| 2008-12-28 14:23:05 |
Alexander Sack |
network-manager: statusexplanation |
dupe of bug 284298 |
well ... actually this is fixed since intrepid as NM now allows you to set custom DNS in connection editor. if you still see the same as the title says, you are seeing bug 284298. |
|
