RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When "create krb5 conf = no" is not set in smb.conf, net ads join -S server creates a krb5.conf for the domain containing something like:

...
[realms]
REALM = {
 kdc = kdc1-ip
 kdc = kdc2-ip
}

It would be better that when specifying the server with -S it would be the only KDC included in the created krb5.conf to make sure all communication happens with the specified server/KDC only.

Please note that if one wants to force using a certain KDC then also master_kdc must be set, see https://bugzilla.redhat.com/show_bug.cgi?id=859961.

Version-Release number of selected component (if applicable):
RHEL 6.3

FWIW, this is related to bug 748831 where net ads join occasionally fails due to fact that different (K)DCs are being contacted during join and they haven't had the time to sync while joining.

Günther, what do you think. Is this worth implementing upstream. -S is probably the wrong option but a new one could be added.

Samba's private krb5.conf is regular overriden, so it does not make sense to to write is once in a special way. If the system really should only connect to one DC then /etc/krb5.conf would be the better way to configure this. To make sure samba talks to a single DC as long as possible the locator plugin should be installed and winbind should run.