Description of problem: AD DNS timestamps have strange values. SSSD is configured with 'dyndns_update = True' entry. But DNS timestamp in AD have strange value after the entry is added. Here is an example: Date on AD machine is '5/9/2013 3:24 PM', but added DNS entry has timestamp '5/9/2013 3:00:00' I think it is strange, but maybe it is a problem on AD side. Version-Release number of selected component (if applicable): How reproducible: sssd-1.10.0-4.fc19 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
SSSD has nothing to do with the timestamps, it just sends the nsupdate to AD, the timestamps are generated by AD.
I double checked the Microsoft documentation to make sure the timestamps are expected. Turns out they are, AD generates the timestamps rounded down to the nearest hour: See for example: http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx?Redirected=true But you're right that we didn't mention this explicitly prior to the test day. I will amend our test plans accordingly. Thanks!