Bug 961363
Summary: | AD DNS timestamps have strange values | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Spurek <dspurek> |
Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | ebenes, jhrozek, pbrezina, sbose, sgallagh, ssorce |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-16 15:43:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Spurek
2013-05-09 13:27:36 UTC
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! |