Bug 163892

Summary: krb5 utils cannot search for KDC in AD realm
Product: [Fedora] Fedora Reporter: Michael Brown <michael>
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-26 23:50:29 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
My krb5.conf none

Description Michael Brown 2005-07-21 15:58:11 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
kinit, k* utils cannot search for the KDC in AD domains anymore. It used to work, with the same config, under older versions (for example, krb5-workstation-1.3.4-12 from RHEL4

Version-Release number of selected component (if applicable):
krb5-workstation-1.4.1-5

How reproducible:
Always

Steps to Reproduce:
1. In /etc/krb5.conf:
[realms]
 AD.DOMAIN = { kdc = AD.DOMAIN }
2. kinit


Actual Results:  kinit(v5): Cannot resolve network address for KDC in requested realm while getting initial credentials

Expected Results:  Password for michael@AD.DOMAIN: ... (working normally)

Additional info:

Other less recent versions of krb5-utils work. I notice that none of them try to do IPV6 lookups, while the failing version does.
Comment 1 Michael Brown 2005-07-21 15:59:47 EDT
Created attachment 117029 [details]
My krb5.conf
Comment 2 Michael Brown 2005-07-21 16:01:32 EDT
Oh yeah - it starts to work when I specify one/multiple IP addresses for the DCs
in the kdc= line in krb5.conf
Comment 3 Christian Iseli 2007-01-22 05:07:41 EST
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.
Comment 4 petrosyan 2008-02-26 23:50:29 EST
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.