NM-generated resolv.conf contains both "domain" and "search" even though the second option supersedes the first one
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
$ cat /etc/resolv.conf
# Generated by NetworkManager
domain langfeldt.net
search langfeldt.net
nameserver 192.168.1.1
man resolv.conf:
The domain and search keywords are mutually exclusive. If more than one instance of these keywords is
present, the last instance wins.
To avoid surprising people that don't know better (or changes in named.conf) and to observe the Robustness principle (http://
Regards,
Nicolai
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CRDA:
country NO:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Date: Sun May 27 23:54:44 2012
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.9 metric 2
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcEnviron:
LANGUAGE=
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-05-20 (7 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet unavailable /org/freedeskto
wlan0 802-11-wireless connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.4.0 connected enabled enabled enabled enabled disabled
summary: |
- "domain" and "search" are mutually exclusive in resolv.conf + NM-generated resolv.conf contains both "domain" and "search" even though + the second option supersedes the first one |
Actual impact is low to minimal, so setting the bug as Triaged/Low. This should be relatively easy to debug in NM code and to fix; but it will need care just to make sure things don't get busted by changes; so it would benefit upstream input.