Indeed, it would be.
The question is, should we change this, considering that we've already
removed such behavior for the hostname.
Arguable, it's simpler and safer to change the domain name...
What does this affect? Does the current behavior break something besides
the output of hostname/fqdn?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1059520
Title:
dnsdomainname not set from DHCP
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
network manager is using DHCP to request an IP address.
root 14465 0.0 0.1 10184 3756 ? S 13:08 0:00
/sbin/dhclient -d -4 -sf /usr/lib/NetworkManager/nm-dhcp-client.action
-pf /var/run/sendsigs.omit.d/network-manager.dhclient-eth0.pid -lf
/var/lib/dhcp/dhclient-e8aec25f-e171-4d3c-99e1-07ed1b3384bd-eth0.lease
-cf /var/run/nm-dhclient-eth0.conf eth0
The lease file contains:
$ fgrep -i domain
/var/lib/dhcp/dhclient-e8aec25f-e171-4d3c-99e1-07ed1b3384bd-eth0.lease
option domain-name-servers 141.42.2.22,141.42.1.11;
option domain-name "charite.de";
Yet I'm seeing this:
$ hostname
senftopf
$ hostname -f
senftopf
$ hostname -d
$
As you can see from the output, the FQDN is "senftopf" (which is clearly
wrong, since it doesn't contain any domain part).
Yet the DHCP server transmits "option domain-name "charite.de";" which is
seemingly ignored.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: network-manager 0.9.6.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Mon Oct 1 13:10:14 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IpRoute:
default via 141.42.231.1 dev eth0 proto static
141.42.231.0/24 dev eth0 proto kernel scope link src 141.42.231.227
metric 1
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
virbr0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to quantal on 2012-09-07 (24 days ago)
nmcli-con:
NAME UUID TYPE
TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
Wired connection 1 e8aec25f-e171-4d3c-99e1-07ed1b3384bd
802-3-ethernet 1349089717 Mon 01 Oct 2012 01:08:37 PM CEST yes
no /org/freedesktop/NetworkManager/Settings/1
IVBB a9a5a623-6ec6-48f8-99eb-ee5cacedfcd4 vpn
1339656433 Thu 14 Jun 2012 08:47:13 AM CEST no no
/org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet connected
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.6.0 connected enabled enabled
enabled enabled disabled
no_proxy: charite.de
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1059520/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
