Samba dynamic DNS updates vs. SSSD behavior

Hello,

I installed Samba on four Debian 13 machines and joined them to an AD domain. Initially, four DNS A records were automatically created, but I accidentally deleted one of them.

I expected the record to be automatically recreated or updated upon a server reboot, a service restart, or just periodically (similar to how SSSD behaves when dyndns_update = true).

However, after restarting the server and the service, and waiting for 24 hours, the DNS entry was still missing. I eventually ran net ads dns register -P, which successfully recreated the record.

Questions:

• Should Samba automatically create and update DNS entries the way SSSD does?
• If it should, why didn't it work in my case? Could it be an issue with my configuration (see below)?
• If Samba is not supposed to update them automatically, is there a risk that these DNS records will eventually be deleted since I have DNS scavenging enabled on the DCs? I've seen some people mention using a cron job to periodically run net ads dns register is that the recommended workaround? Or just add static entries?

​

[global] security = ads allow dns updates = secure only smb encrypt = enabled server signing = mandatory disable netbios = yes map to guest = bad user log level = 1 max log size = 0 workgroup = XX netbios name = STORAGE3 realm = ad.xx.xx password server = * idmap config * : backend = tdb idmap config * : range = 5000-9999 idmap config XX: backend = ad idmap config XX: schema_mode = rfc2307 idmap config XX: range = 10000-99999 idmap config XX: unix_nss_info = yes idmap config XX: unix_primary_group = yes winbind refresh tickets = yes winbind cache time = 3600 winbind reconnect delay = 30 winbind offline logon = yes winbind use default domain = yes winbind enum users = yes winbind enum groups = yes winbind expand groups = 1 kerberos method = system keytab ntlm auth = ntlmv2-only 

Thank you,