Bug 1144343

KDC's can be used to canonicalize server names even if they don't have the domain.com suffix, but this isn't present by default in MIT krb5.

(In reply to Stef Walter from comment #0)
> By default realmd should rename the hostname of the computer to
> computer.domain.com. Without this, the machine is not ready to be used via
> kerberos, etc.

What does realmd do now (what is the hostname now)?

How would realmd determine the computer.domain.com name?

Isn't it the question of DNS?
Does it really matter what host thinks its host name is?
I thought that the client would need to resolve the host it is connecting to and if it resolves to the name that matches the principal the host has you should be all set. No?

You're right. In addition it appears (at least with AD) canonicalization of host names without the domain works as expected. Will post more findings here. So many things going on at once, I've neglected to update this bug.

(In reply to Dmitri Pal from comment #3)
> Isn't it the question of DNS?
> Does it really matter what host thinks its host name is?

It does because that's the principal it will use. And if the hostname is outside of the domains currently maintained by IPA, IPA will create new DNS zone for the machine, it seems.

> I thought that the client would need to resolve the host it is connecting to
> and if it resolves to the name that matches the principal the host has you
> should be all set. No?

"Resolve the host it is connecting to"? That's the server, isn't it?

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.