[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Hostnames and Active Directory

Stef, thanks for heads up, we are probably adding
hostname setting to UI in network spoke for F18.

We still don't set the hostname for installer environment,
currently it is only set by NM when a connection is activated
(its policy is 1) configuration file 2) dhcp 3) configuration file
in time of NM start 4) address lookup 5) "localhost").
So for example --hostname configured in kickstart is not
applied in installer environment.


On 12/17/2012 10:31 AM, Stef Walter wrote:
Hey all (sorry for starting a new thread about this, just subscribed)...

I'd just like to pitch in and say that having a valid hostname is also
needed for joining an Active Directory or FreeIPA domain from within

A kerberos computer account principal is created based on the hostname
(as in gethostname()) of the machine. The keytab of the machine will
contain the hostname too.

So in order to join a domain from the Anaconda UI, we have to have setup
a host name before the post install configuration. This means that (for
the AD/FreeIPA use case) it's sufficient to have the hostname in the
progress 'spoke', as Chris pointed out:


We would theoretically block on prompting for a the hostname if joining
a domain.

Somewhat related: In the case of kickstart, we currently assume that the
admin has setup some sort of way to distribute unique host names (either
via DHCP or munging the kickstart files as they're served). Perhaps this
can be fine tuned in the future.



Anaconda-devel-list mailing list
Anaconda-devel-list redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]