Hi Nico,

Nico Kadel-Garcia <[log in to unmask]>
writes:

[snip (27 lines)]

> "system-config-network-tui" works pretty well if installed.

I've had a look at the settings with this, and the setting are as I
expect.

> The problem is that the $HOSTNAME for the system isn't published in
> DNS, nor is it the first hostname for a line in /etc/hosts, so the
> "hostname --fqdn" is not finding it associated with your IP addresses.

I may have explained it badly, but 'hostname --fqdn' works as expected:

  [root@tadmin01 ~]# hostname -f
  tadmin01.test.cluster

  [root@tadmin02 ~]# hostname -f
  tadmin02.test.cluster

The difference is when I call 'hostname' *without* any option:

  [root@tadmin01 ~]# hostname
  tadmin01

  [root@tadmin02 ~]# hostname
  tadmin02.test.cluster

> The usual approach for portable laptops is to put a line like this in
> /etc/hosts somewhere.
>
>     127.0.0.1 mymachine.mydomain
>
> Do *not* put this.
>
>     127.0.0.1 mymachine mymachine.mydomain
>
> And do not touch the line for localhost, the way some installers do.
>
>     127.0.0.1  localhost.localdomain localhost localhost4.localdomain
> localhost4 mymachine.mydomain mymachine
>
> That last one is very common with a lot of bad, bad, software
> installers and configuration tools. Use a *different line* for the
> FQDN.
>
> Note that some software also may work better if you have the hostname
> tied to the systems's live IP addresses, but that's usually because
> it's bad software.

/etc/host looks like this (except with real external IP addresses) on
both machines:

  127.0.0.1	  localhost.localdomain localhost
  ::1		  localhost6.localdomain6 localhost6

  xxx.xxx.xxx.xxx tadmin01.zedat.fu-berlin.de
  xxx.xxx.xxx.xxx tadmin02.zedat.fu-berlin.de
  10.141.235.254  tadmin01.test.cluster tadmin01
  10.141.235.253  tadmin02.test.cluster tadmin02

But as they are identical, it shouldn't be the source of the
difference.

Cheers,

Loris

-- 
This signature is currently under construction.