I am going to be so bold as to close this bug report. The original
report (from 2004) and followups reflect the way Ubuntu was installed
and what NetworkManager and other software did a long time ago and the
subsequent discussion is not clearly about any one issue. If there are
still outstanding
Looking through this again, while I agree there might be a need to
clarify the way that the fqdn, /etc/hostname and /etc/hosts files and
such are being used, this is not a bug in NetworkManager and as far as I
am concerned, NM is doing what it should (and so is netcfg, but I'll let
Colin close
Although problems with resolving the local hostname appear finally to be
getting solved, I think it would still be good to create an explicit
policy describing the (default) contents of /etc/hostname,
/etc/nsswitch.conf and /etc/hosts. The policy should also describe how
applications are expected
I'd agree that having a formal policy for this (presuming there isn't
one already, buried somewhere) is an excellent idea. The Debian folks
have the Debian Policy Manual, and *everyone* abides by it. The clarity
that that approach provides would certainly be welcome here.
--
You received this
$ hostname -f
kubuntu
$ lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/8980
Title:
hostname -f does not return a proper FQDN
--
network-manager appears to be working sanely now, in Natty.
Could anyone affected by this bug in recent memory please check to see
if the problem persists in the latest released Ubuntu?
(It would be nice to finally close this report, after almost seven
years...)
--
You received this bug
At last I got hostname -i and hostname -f to work (hostname -I did work all the
time).
In my case, the setup of dhclient and the DSL modem did not play well together:
https://bugs.launchpad.net/ubuntu/+source/dhcp/+bug/694290
furthermore, I have adjusted /etc/hosts along the lines in this bug.
FYI It looks like this issue is also being discussed in the following
bug reports.
Hostname change blocks backup after upgrade to maverick
https://bugs.launchpad.net/duplicity/+bug/662334
NetworkManage does not set domain in /etc/hosts on DHCP connections
Here is my view of the problem: On an up-to-date Maverick install, if
/etc/hosts looks like the following on bootup...
127.0.0.1 localhost
127.0.1.1 hostname.intra.example.com hostname
# The following lines are desirable for IPv6 capable hosts
::1 localhost
Hello,
it also prevents duplicity (Backup Software) from running:
Last full backup date: Tue Nov 2 10:12:12 2010
Fatal Error: Backup source host has changed.
Current hostname: localhost6.localdomain6
Previous hostname: lain.office.noris.de
Aborting because you may have accidentally tried to
In Maverick, the rewrite of /etc/hosts causes the idmapd daemon to
think that the current domain is localdomain.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
... no, that's not the only thing; does Network Manager set the hostname
to localhost.localdomain? Because fixing /etc/hosts with chattr +i
when running networkmanager will still cause idmapd to think that it's
current domain is localdomain.
--
hostname -f does not return a proper FQDN
In Maverick, NetworkManager already does rewrite /etc/hosts with some
amounts of success.
FWIW, I can also pretty nicely workaround having the FQDN available or
not by adding just the domain part in /etc/domainname. It's not pretty
but it does work, and from there on connection I have /etc/hosts
Does this issue occur in Lucid?
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: netcfg (Ubuntu)
Status: Confirmed = Incomplete
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug
Yes. And in Maverick.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: netcfg (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: netcfg (Ubuntu)
Assignee: Colin Watson (cjwatson) = (unassigned)
--
hostname -f does not return a proper FQDN
I think the two issues here should be disentangled. In particular I
think the problem with NetworkManager should be split out and tracked as
a separate bug.
To be clear the problem with NetworkManager is that it doesn't take the
complete set of actions necessary so that hostname -f and
I just did test installs of 8.04.2 and 9.04 alpha 3, using the i386
alternate ISO in each case. I answered the question about the hostname
by supplying the FQDN in each case. Immediately on completion of each
install, I checked the various files.
For the jaunty alpha, the domain was correctly
We do still seem to have some problems:
127.0.0.1 sarantium localhost.localdomain localhost
127.0.1.1 sarantium.pelham.vpn.ucam.org sarantium
This machine was originally installed with an alpha CD of gutsy, dated
20070911. This is, to say the least, odd since netcfg at the
Ah, I see what the problem is! network-manager overwrites /etc/hosts
with a bogus version that:
* sticks the short hostname into 127.0.0.1, when it was already in 127.0.1.1
previously
* gratuitously adds localhost.localdomain
The result of this is indeed that 'hostname -f' stops returning
Scott Kitterman says on IRC that he has seen this on servers without
NetworkManager. In that case, I need to see the /etc/hosts file, and I
need to know what the machine was installed from (the simplest way to
tell me this is to attach /var/log/installer/syslog). Please do not
reassign this bug
hostname -f
mailout02
** Also affects: netcfg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcfg (Ubuntu)
Status: New = Confirmed
** Attachment added: etc/hosts
http://launchpadlibrarian.net/21541129/hosts
--
hostname -f does not return a proper FQDN
** Attachment added: Installer log
http://launchpadlibrarian.net/21541144/syslog
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
** Attachment added: resolv.conf
http://launchpadlibrarian.net/21542366/resolv.conf
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
** Attachment added: questions.dat
http://launchpadlibrarian.net/21543121/questions.dat
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
As far as I can tell from Scott's logs, he simply didn't tell netcfg
about his domain name at installation time, and so it couldn't write it
to /etc/hosts.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a
I have a vague recollection that in some cases I got asked and in some I
didn't, but it's been a while sine I did this install. I'm sure if I got
asked, I'd have answered.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification
I think the hostname question is not particularly clear about the fact
that you can enter an FQDN (the expectation upstream is that a separate
domain question would be asked, but we decided it only needed one
question). We should fix this.
** Changed in: netcfg (Ubuntu)
Importance: Undecided =
** Changed in: netcfg (Ubuntu)
Assignee: (unassigned) = Colin Watson (kamion)
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
That hostname -i returns 127.0.1.1 is not a bug.
In contemporary Debian and Ubuntu, /etc/hosts should look like this:
127.0.0.1 localhost
127.0.1.1 foo
where foo is the Linux hostname and the content of /etc/hostname.
If the machine has a permanent IP address (123.45.67.89) and FQDN
** Tags added: qa-jaunty-foundations
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Still present in Intrepid too.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
JMX services are also affected by the incorrect response provided by 'hostname
-i'.
This seems to be more a DHCP problem than anything else.
Once a valid DHCP lease is obtained, the /etc/hosts file should have a proper
configuration set.
This is the root of all evil :)
PS.: The issue is still
This also causes problems with winbind/samba, since 'net ads join'
cannot join the domain unless the domain portion of the hostname matches
the AD domain/realm
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a
Note that the sudo/hostname combo bug still applies to Hardy:
just updated to 8.04 and that either messed up my hostname or it's not good
for sudo anymore, I'm a bit confused at the moment
https://bugs.edge.launchpad.net/ubuntu/+source/sudo/+bug/32906
--
hostname -f does not return a proper
What's this concern about losing sudo access? The comment
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/8980/comments/20
is the first time it has been mentioned here.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification
davee,
Check these out:
http://www.google.com/search?q=hostname+sudo+ubuntu
Which turns up: (among others)
https://bugs.edge.launchpad.net/ubuntu/+source/sudo/+bug/32906
https://bugs.edge.launchpad.net/ubuntu/+source/sudo/+bug/188424
https://bugs.launchpad.net/bugs/9471
Wow this is a 4-year old bug! and still Confirmed
Ubuntu is dealing with 'enterprise-grade servers' and we have a bug about
/etc/hosts ???
How is this a helpful comment?
Do you have further information about this bug? Does it still happen in
a fresh install of recent release?
I'm guessing
I think I'm an experienced admin.
I just setup two load balanced Ruby on Rails Mongrel cluster
applications with Apache 2 and proxy_balancer with less difficulty than
I had trying to make sure I had the server's hostname properly (with the
added intimidation that I could lose sudo access!) :-(
Personally I've had no trouble with sudo. I'm not sure what that's about.
This really isn't more than a nuisance for an experienced admin, but it
would be nice to get it fixed.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug
Still happens on a fresh gutsy install.
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have to admit my comment wasn't helpful at all.
I don't have sudo problems yet (and NOT looking forward to it!
Especially not on a remote server.)
But there are some things:
* I never had any idea that /etc/hosts has a connection with the wellbeingness
of sudo
* I've had sudo problems a few
Wow this is a 4-year old bug! and still Confirmed
Ubuntu is dealing with 'enterprise-grade servers' and we have a bug
about /etc/hosts ???
--
hostname -f does not return a proper FQDN
https://bugs.launchpad.net/bugs/8980
You received this bug notification because you are a member of Ubuntu
[23:23] scotth its a pretty old install that I believe started with dapper
and is now at gutsy
[23:24] * ScottK wonders if Bug #8980 might be relevant.
[23:24] ubotu Launchpad bug 8980 in netcfg hostname -f does not return a
proper FQDN [Medium,Confirmed] https://launchpad.net/bugs/8980
[23:26]
Not necessarily (about the order being important). On both Dapper and
Edgy (as fresh installs) I have (for example):
/etc/hosts
127.0.0.1 localhost
70.91.79.100mailout01.controlledmail.commailout01
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost
I have a system that started as breezy, and has been updated to dapper then
edgy.
My hostname is 'marvin'.
By default, the first entry in /etc/hosts read
127.0.0.1 localhost.localdomain localhost marvin
A later entry reads
192.168.13.2 marvin.chile.gen.nz marvin
If I move the localhost entry
I think I understand this better now... I built a new server today and
running the same script I get:
Python 2.4.3 (#2, Apr 27 2006, 14:43:58)
[GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2
Type help, copyright, credits or license for more information.
import socket
print socket.getfqdn()
This problem is still present in Dapper. Among other things it affects
the ability of Postfix to operate as configured in Ubuntu:
From Postconf 5:
http://www.postfix.org/postconf.5.html#myhostname
The default is to use the fully-qualified domain name from
gethostname.
So, Postfix is expecting
48 matches
Mail list logo
