I think it was not having dynamic updates enabled for the reverse zone.
I enabled those and PTR sync on both the forward and reverse and now it
seems to be working for a new client that I joined.
What I'm not clear on at this point is why that is not a default
setting. I know at some point
Hi,
can you check the journalctl -u named(-pkcs11) on server, they might be
errors why PTR record has not been added.
Do you have enabled dynamic updates for the reverse zone?
Martin
On 09/12/2015 10:42 PM, Youenn PIOLET wrote:
Hi,
I've seen the same issue recently on various clients
Hi,
I've seen the same issue recently on various clients using ipa 3.3 and ipa
4.* during the first join on a clean OS. Can't confirm it was working
before. Is it normal behavior?
Allow PTR sync is enabled.
Cheers,
Le 12 sept. 2015 7:44 AM, "Nathan Peters" a
écrit :
>
On Fri, 2015-09-11 at 10:25 -0700, nat...@nathanpeters.com wrote:
> I have been trying to figure this out for a while now but when I join
> machine to FreeIPA, the installer properly creates forward DNS
> entries,and DNSSSHFP entries, but does not create reverse entries.
> Without the PTR
I have been trying to figure this out for a while now but when I join a
machine to FreeIPA, the installer properly creates forward DNS entries,
and DNSSSHFP entries, but does not create reverse entries. Without the
PTR records, kerberos logins are always failing on these machines.
The reverse
On 9/11/2015 10:32 AM, Simo Sorce wrote:
On Fri, 2015-09-11 at 10:25 -0700, nat...@nathanpeters.com wrote:
I have been trying to figure this out for a while now but when I join
machine to FreeIPA, the installer properly creates forward DNS
entries,and DNSSSHFP entries, but does not create