I figured out the problem. It appears that the ipa-client-automount looks at
the default domain name configured on the client and then queries that for srv
records. In our case, the default domain name is not the same as the IDM
domain.
___
FreeIPA-u
Rob,
Thanks for that. I am aware of that tool and we used it to populate our
external DNS server. I can verify that all of the records identified do
exist in the DNS zone.
-Scott
On Fri, Nov 27, 2020 at 2:09 PM Rob Crittenden wrote:
> Scott Dungan via FreeIPA-users wrote:
> > When attempting t
Scott Dungan via FreeIPA-users wrote:
> When attempting to setup a domain client to query the domain for automounts,
> we see the following:
>
> ipa-client-automount --location=default
> Searching for IPA server...
> Autodiscovery was successful but didn't return a server
>
> If we specify a ser
Hi Flo,
I've raised that issue as requested including this full email chain so far:
https://pagure.io/freeipa/issue/8600
Sorry to seem dense, but ssl certs and keys are definatly not my strong suite,
and the whole freeipa setup se have was sort of dumped on me when my colleague
who was looking
When attempting to setup a domain client to query the domain for automounts, we
see the following:
ipa-client-automount --location=default
Searching for IPA server...
Autodiscovery was successful but didn't return a server
If we specify a server it works:
ipa-client-automount --location=default
On 11/27/20 11:54 AM, Marc Pearson | i-Neda Ltd wrote:
Hi Flo,
I've raised that issue as requested including this full email chain so far:
https://pagure.io/freeipa/issue/8600
Sorry to seem dense, but ssl certs and keys are definatly not my strong suite,
and the whole freeipa setup se have wa
On Fri, Nov 27, 2020 at 06:17:40AM -, mir mal via FreeIPA-users wrote:
> Hi,
>
> Sorry, maybe I wasn't detailed enough. The environments are client Ubuntu
> 20.04, FreeIPA Fedora 32 - freeipa-server-4.8.9-2.fc32.x86_64
> It's an odd behaviour which should really not happen in a live environme
