[Bug 8980] Re: hostname -f does not return a proper FQDN

[Thomas Hood]

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 to interpret the contents of these files.
Policy should take into account the fact that some computers are not
connected to a network; some are connected to the Internet and have a
static IP address; some get an IP address via DHCP; some of the latter
also get assigned a FQDN.  Obviously, applications should work correctly
under all circumstances.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netcfg in Ubuntu.
https://bugs.launchpad.net/bugs/8980

Title:
  hostname -f does not return a proper FQDN

Status in “netcfg” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  If you start a remote desktop session off, it only gives you the connection
  string for localhost.
  i.e: localhost.localdomain:0 

  This should be either the actuall machine name (i.e. fqdn) or the IP address.
  If this is sent to a 3rd person, they would only be trying to connect to themselfs, 
  rather than the actual target machine.

  My machine is fully up to date and is running a FQDN as resolved from
  internal DNS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/8980/+subscriptions