search for: bind910

...> > What do you mean '*in alternative*' ?? I mean when I build Samba port, I can choose NSUPDATE *or* BIND99 *or* BIN910 (where "or" means "exclusive or", I can choose at most one). Those options are described as: BIND99 = Use bind99 as AD DC DNS server frontend BIND910 = Use bind910 as AD DC DNS server frontend NSUPDATE = Use samba NSUPDATE utility for AD DC Notice this options only serve the purpose of tracking dependencies between packages; they do not mess with the way Samba is compiled or configured. Choosing NSUPDATE brings in another port/package, nam...

...in alternative*' ?? > > I mean when I build Samba port, I can choose NSUPDATE *or* BIND99 *or* > BIN910 (where "or" means "exclusive or", I can choose at most one). > > Those options are described as: > BIND99 = Use bind99 as AD DC DNS server frontend > BIND910 = Use bind910 as AD DC DNS server frontend OK, these are just what version of bind to use. > NSUPDATE = Use samba NSUPDATE utility for AD DC I think this means use the internal SAMBA DNS server and install nsupdate (which on Devuan, means install dnsutils) > > Notice this options only...

On 05/03/16 22:55, Rowland penny wrote: > Don't use freebsd, but Samba 4, when run as an AD DC, uses nsupdate to > update a computers DNS records in AD. First off, thanks for answering. Alas, I don't really understand what you mean... Is it used to dynamically add A records for clients that connect to the AD? >> Is it intended to work with BIND (like the other two in