On 27/10/2016 10:07, Brian Candler wrote:
To the OP: in that case, I'd still recommend that you choose a
distinct kerberos realm like IPA.YOURCOMPANY.COM, with associated
primary domain "ipa.yourcompany.com", and let FreeIPA manage that
domain so that it sets up all the right SRV records for
On to, 27 loka 2016, Brian Candler wrote:
On 27/10/2016 10:07, Brian Candler wrote:
To the OP: in that case, I'd still recommend that you choose a
distinct kerberos realm like IPA.YOURCOMPANY.COM, with associated
primary domain "ipa.yourcompany.com", and let FreeIPA manage that
domain so that
On 27/10/2016 09:30, Alexander Bokovoy wrote:
Yes, you can do that, there is no issue at all.
Thank you for confirming that.
To the OP: in that case, I'd still recommend that you choose a distinct
kerberos realm like IPA.YOURCOMPANY.COM, with associated primary domain
"ipa.yourcompany.com",
On to, 27 loka 2016, Brian Candler wrote:
On 26/10/2016 21:03, Ranbir wrote:
If I have two networks, say A and B, and I want both to use the same
FreeIPA server, should I have one Freeipa domain for network A and a
sub-domain for network B, (domain.local and b.domain.local), or
should I
On ke, 26 loka 2016, Ranbir wrote:
Hi Everyone!
If I have two networks, say A and B, and I want both to use the same
FreeIPA server, should I have one Freeipa domain for network A and a
sub-domain for network B, (domain.local and b.domain.local), or should
I create two top level domains
Hi Everyone!
If I have two networks, say A and B, and I want both to use the same
FreeIPA server, should I have one Freeipa domain for network A and a
sub-domain for network B, (domain.local and b.domain.local), or should I
create two top level domains (a.local and b.local)? What's the