Bug 8894 - RFE: Implement DNS registration update/refresh
Summary: RFE: Implement DNS registration update/refresh
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 4.13.3
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2012-04-25 14:40 UTC by Guenther Deschner
Modified: 2020-12-29 11:36 UTC (History)
6 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Guenther Deschner 2012-04-25 14:40:58 UTC
AD domains often use DNS scavenging [1] 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

Comment 1 David Woodhouse 2015-04-23 08:34:23 UTC
'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.
Comment 2 James Johnston 2016-05-16 02:50:30 UTC
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.
Comment 3 Amit Kumar 2017-03-21 11:58:53 UTC
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?
Comment 4 Andreas Schneider 2017-08-14 14:27:47 UTC
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.
Comment 5 Stefan Metzmacher 2017-08-14 14:36:46 UTC
(In reply to Andreas Schneider from comment #4)

Winbind already monitors some local addresses via netlink sockets...
Comment 6 Björn Jacke 2020-12-29 11:36:13 UTC
yes, the netlink socket monitoring should also trigger DNS updates I think. Can we hook this up into source3/lib/addrchange.c directly?