Ok I have pointed the domain to my IP address (also setup DDNS with the
registrar). Howevver BIND still fails.
Nov 14 20:46:28 freeipa01.asm.caprica.space named-pkcs11[23802]: starting BIND
9.11.4-P2-RedHat-9.11.4-17.P2.el8_0.1 (Extended Support Version)
Nov 14 20:46:28
Andrew Meyer via FreeIPA-users wrote:
> Sure. Give me a bit to gather that.
Could be related to:
2019-11-13T04:02:26Z INFO Checking DNS domain caprica.space., please
wait ...
2019-11-13T04:02:26Z WARNING DNS zone caprica.space. already exists in
DNS and is handled by server(s):
Tristan Weis via FreeIPA-users wrote:
> Hey guys,
>
> I set up my very first FreeIPA installation and I'm currently dealing with an
> issue I hope you can help me with.
> I'm running FreeIPA version 4.7.1 on CentOS 8. I installed about 3 weeks ago,
> had been working fine up until a few days
Sure. Give me a bit to gather that.
___
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org
Fedora Code of Conduct:
Andrew Meyer via FreeIPA-users wrote:
> I am trying to migrate to CentOS 8 in my home lab. And I have gotten FreeIPA
> installed. However I am using caprica.space as my domain name but I don't
> think bind/named likes me using that. Is this an issue the version in
> FreeIPA or did I do
I am trying to migrate to CentOS 8 in my home lab. And I have gotten FreeIPA
installed. However I am using caprica.space as my domain name but I don't
think bind/named likes me using that. Is this an issue the version in FreeIPA
or did I do something wrong? I found this out because FreeIPA
Hey guys,
I set up my very first FreeIPA installation and I'm currently dealing with an
issue I hope you can help me with.
I'm running FreeIPA version 4.7.1 on CentOS 8. I installed about 3 weeks ago,
had been working fine up until a few days ago (after a restart).
I'm encountering several
On 14/11/2019 11:44, Alexander Bokovoy wrote:
> On to, 14 marras 2019, lejeczek via FreeIPA-users wrote:
>> hi guys
>>
>> I've have AD trust work fine (gssapi), ssh & samba are password-less
>> when the trust is establish with 'admin' credentials.
>>
>> But the strory is very different with
On to, 14 marras 2019, lejeczek via FreeIPA-users wrote:
hi guys
I've have AD trust work fine (gssapi), ssh & samba are password-less
when the trust is establish with 'admin' credentials.
But the strory is very different with 'shared secret'. Kerberos does not
work, passwords are asked for and
hi guys
I've have AD trust work fine (gssapi), ssh & samba are password-less
when the trust is establish with 'admin' credentials.
But the strory is very different with 'shared secret'. Kerberos does not
work, passwords are asked for and with Windows cifs - asks for username
and no
On to, 14 marras 2019, Per Qvindesland via FreeIPA-users wrote:
On the web ui it says in “Managed Suffix” that the server is domain, ca but
when I go into the page it says:
It is strongly recommended to keep the following services installed on more
than one server:
CA
Which is really odd.
On the web ui it says in “Managed Suffix” that the server is domain, ca but
when I go into the page it says:
It is strongly recommended to keep the following services installed on more
than one server:
CA
Which is really odd.
Regards
Per
> On 13 Nov 2019, at 17:33, Rob Crittenden via
12 matches
Mail list logo
