It means with "dns zone scavenging = yes" records will be expire and removed before they get recreated. MS-DNSP 1.1 Glossary explains NoRefresh interval: If an update which does not change the DNS data for a record set is received within the NoRefresh interval then the DNS server will not update the timestamp on the record. This allows the DNS server to avoid unnecessary updates to the data store. refresh interval: If the NoRefresh interval for a record has expired and the DNS server receives a DNS update that does not change the record data then the DNS server will commit a new timestamp to the data store. The combination of NoRefresh and refresh intervals allows a DNS server to maintain a relatively accurate record timestamp without unnecessary updates to the data store. The default value for both is 168 hours/7 days. Records are deleted after NoRefresh interval + refresh interval Which means 14 days.
It seems the code in dns_common_replace() is doing the correct thing, if fAging is TRUE. But the problem likely is that dns_tombstone_records_zone() doesn't look at fAging at all...
Also a value of 0 in dwNoRefreshInterval or dwRefreshInterval should be mapped to the default from the serverinfo
This bug was referenced in samba master: 8f17d9a89e22d074e6894cc1530ea626d60a080f c239af3b4d55705b96cf371cc1c34910249b2379 03caa23a6d98fb7c252590de9ffc909407b8bdc8 312da01ed1d9c0d0b30bc4db8262e6d01b307252 9919ae52ef611423205a140e32900d84242fc01d fdcda85ac611e2e12ab895674fed76347b5ed6d0 9fe99c5760a1dc22a57e7bf6338a1b2244e4da6d 3f97ac62727137a2b56555a821a2f1ab5113fac2 1146df4c532834481a67cbcf5c7bc8142dfe9875 2cf29c3c95aa4c6bdd645e34fdf521f9bcb91538
Created attachment 19181 [details] Patches for v4-25-test
Created attachment 19182 [details] Patches for v4-24-test
Created attachment 19183 [details] Patches for v4-23-test
This bug was referenced in samba v4-23-test: 346f4c3d7afbf0052b0f515ad4a31ef76f9a32cf 86651510ebd296677d3638ee1e376fcf4a8e5fcc 6c438d6434772405a3680bf9c4470f66671888a8 9f15e0b2e51ffe547b285c0348e500e0686d1def 5b894bb9f876fcd4d7bd787802d1ee5c8a7018a0 67b581726d95f6b75729ce57c4b92a75c43df249 ded1137de43185252704da77d690ea7667e1ac91 c3fa91ca9ea12b2717539ea1a2d908faef982551 fb24eebc21cf6e3b91784dbb5690e46c32d8bda4 77d1c22f4544a73060bf90e2ba9a446978694aaa
This bug was referenced in samba v4-25-test: 6f6d5efa4e018e70615bceb70ab2992a73a4a6d5 f12dd28268c19867ac44328dbd701c828c21a467 f45e23c381b6d23629f0c8d2098c295a1a0ec5f4 ee95e7af9b01063a34c9faa04bbde587d0bcb7f8 ec6a582202dd081bb18c9e8902c0198165218f69 9ca6c0e526c511040c2805d035baadb0b5a73cc6 2ba4e2055cf1c86f7c6853cf364ab9dc34ef948e a4b9c50ffa52a9eb7c01ac51034a5405e7e0703a 81059f726fc973fcbf9d80232dc1962167235c18 d285e69988f8cf438ea8aff8ce2717eaf0825ee4
This bug was referenced in samba v4-24-test: 7036a847f788190b5535be206950fe887964ef97 d87e714b8fabe8a0cf80a0d50ee3d85ed9f9f5db 54565c36561a5809a760eae7e9f0af3018320354 b2c643490b42f0db5bd04962823020d4f1b3a276 59fb4e0b629b0cf19246816609f00308d3109b11 a836a14721f64f1ba11deb70c8505f8032ca1855 1525bf05043144cdfdc49ab156c6ed7aa8299120 674fdb5946003048fa1603e8db6bd26c547994c4 7f00cbbd1ecf24e83ff7f9e81dac1f99996c6976 c5e2a6d602a85a72d3ace1471e5f77070235716b
This bug was referenced in samba v4-23-stable (Release samba-4.23.12): 346f4c3d7afbf0052b0f515ad4a31ef76f9a32cf 86651510ebd296677d3638ee1e376fcf4a8e5fcc 6c438d6434772405a3680bf9c4470f66671888a8 9f15e0b2e51ffe547b285c0348e500e0686d1def 5b894bb9f876fcd4d7bd787802d1ee5c8a7018a0 67b581726d95f6b75729ce57c4b92a75c43df249 ded1137de43185252704da77d690ea7667e1ac91 c3fa91ca9ea12b2717539ea1a2d908faef982551 fb24eebc21cf6e3b91784dbb5690e46c32d8bda4 77d1c22f4544a73060bf90e2ba9a446978694aaa
This bug was referenced in samba v4-25-stable (Release samba-4.25.0rc2): 6f6d5efa4e018e70615bceb70ab2992a73a4a6d5 f12dd28268c19867ac44328dbd701c828c21a467 f45e23c381b6d23629f0c8d2098c295a1a0ec5f4 ee95e7af9b01063a34c9faa04bbde587d0bcb7f8 ec6a582202dd081bb18c9e8902c0198165218f69 9ca6c0e526c511040c2805d035baadb0b5a73cc6 2ba4e2055cf1c86f7c6853cf364ab9dc34ef948e a4b9c50ffa52a9eb7c01ac51034a5405e7e0703a 81059f726fc973fcbf9d80232dc1962167235c18 d285e69988f8cf438ea8aff8ce2717eaf0825ee4
This bug was referenced in samba v4-24-stable (Release samba-4.24.7): 7036a847f788190b5535be206950fe887964ef97 d87e714b8fabe8a0cf80a0d50ee3d85ed9f9f5db 54565c36561a5809a760eae7e9f0af3018320354 b2c643490b42f0db5bd04962823020d4f1b3a276 59fb4e0b629b0cf19246816609f00308d3109b11 a836a14721f64f1ba11deb70c8505f8032ca1855 1525bf05043144cdfdc49ab156c6ed7aa8299120 674fdb5946003048fa1603e8db6bd26c547994c4 7f00cbbd1ecf24e83ff7f9e81dac1f99996c6976 c5e2a6d602a85a72d3ace1471e5f77070235716b