AD domains often use DNS scavenging  meaning that DNS entries for domain
members which have not been refreshed in a certain period of time will be
removed. Windows domain members refresh their DNS registrations daily but Samba
does offer such an option currently. It is of course possible to use something
like "net ads dns register -P" in daily cron but this is rather inelegant.
Samba/winbind should automatically refresh AD DNS registration if so
'net ads dns register' doesn't really work very well anyway; see bug 7634.
I ended up scripting calls to 'nsupdate' to set the forward and reverse DNS, in a NetworkManager dispatcher script.
Not only should SAMBA update DNS by way of "net ads dns register" every 24 hours, but it should also update whenever the IP addresses of the system change, for both IPv4 and IPv6. For example, suppose DHCP decides to give SAMBA a new IP address - then SAMBA needs to update DNS immediately.
Any plans for fixing up in upcoming samba release?
For me, It around an year working on samba, AD integration & it interests me. Can this bug assigned to me?
Looking at comment #2 I think we need to improve 'net ads dns' and provide a script for NetworkManager. That's probably the only way to do this correctly.
I'm not sure winbind is the right place here to detect client ip changes to do updates.
(In reply to Andreas Schneider from comment #4)
Winbind already monitors some local addresses via netlink sockets...
yes, the netlink socket monitoring should also trigger DNS updates I think. Can we hook this up into source3/lib/addrchange.c directly?