On 23/05/14 13:14, Jakub Hrozek wrote:
On Fri, May 23, 2014 at 12:54:59PM +0200, steve wrote:
On 23/05/14 12:43, Jakub Hrozek wrote:
On Fri, May 23, 2014 at 12:10:14PM +0200, steve wrote:
Would it be possible to include the PTR update as part of the ad backend?
Cheers,
Steve
According to man sssd-ad, dyndns_update_ptr should be set to True in the
AD backend. Do you not see the PTR records updated? Anything interesting
in the logs?
We only get A and AAAA:
(Thu May 22 12:18:20 2014) [sssd[be[hh3.site]]]
[be_nsupdate_create_fwd_msg] (0x0400): -- Begin nsupdate message --
realm HH3.SITE
update delete lubuntu-laptop. in A
send
update delete lubuntu-laptop. in AAAA
send
update add lubuntu-laptop. 3600 in A 192.168.1.22
send
The PTR update is a separate one, I need to see more context from the
logs.
If the PTR update was off, you would see a DEBUG message from
"sdap_dyndns_update_done" saying "No PTR update requested, done\n"
Sorry. Our test bind didn't have a reverse. Duh.
_______________________________________________
sssd-users mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/sssd-users
