Learn more about these different git repos.
Other Git URLs
Utilising Dynamic DNS (DDNS) with SSSD is not updating the timestamp for A records. PTR records are updating the timestamp without issue. The cause of this issue is because only a single transaction is used for the deletion and creation of the A record, while the PTR record is split into 2 transactions. This behaviour is identical when performed manually through nsupdate. Only after splitting the transaction in 2, does the timestamp of the A record update. This is a big issue when scavenging is enabled.
DNS: Windows Server 2012 R2 Client: CentOS 7 Domain: Active Directory SSSD: sssd-1.15.2-50.el7_4.8.x86_64 bind-utils: bind-utils-9.9.4-51.el7_4.2.x86_64
My assumption is that the Windows DNS evaluates the end result of a transaction in comparison to the current configuration and applies that end result, rather than literally following every instruction to the letter. In the case of an A record, the end result is identical to the current configuration of the DNS server (except for the timestamp), so it doesn't make any changes.
This is most likely expected behaviour, due to the norefresh behaviour of the Windows DNS server: "When a DNS record is created by a new client, the NoRefresh interval is in effect. When the client dynamically updates its DNS information in this situation, the client's DNS time stamp is not updated until the Refresh interval takes effect. This behavior prevents the replication of lots of DNS objects in the Active Directory directory service." https://support.microsoft.com/en-us/help/932464/how-dns-dynamic-updates-work-together-with-the-dns-aging-and-scavengin
Metadata Update from @silae: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4674
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.