The magic of determining all addresses for dns updates in "net ads join" and "net ads dns register" is useless and leads to wrong results if "clustering = yes". Firstly, it only takes into account the addresses local to the node on which the command is run. Secondly, it usually assigns too many addresses from the node: In clustered samba, samba usually listens on the wildcard interface but effectively serves only the addresses that are ctdb's "public addresses". So the default behaviour is wrong for "clustering = yes".
Created attachment 6136 [details] patchset for master This is a patchset for master. It does two things: 1. disables the dns updates for net ads join if "clustering = yes" 2. adds support for specifying IPs on the commandline of "net ads dns register" and refuses to do updates if "clustering = yes " and no IPs are explicitly specified. Comments, please....
I'll extend the patches to support "cluster addresses" and push them to master and v3-6-test. I'll propose a backport for 3.5.x here.
Created attachment 6151 [details] Backport Patch for v3-5-test
Comment on attachment 6151 [details] Backport Patch for v3-5-test Metze, thanks for extending this to use cluster addresses. I was not aware that it was so easy. :-) Karolin: please pick for 3.5.7
==> Karolin
Pushed to v3-5-test. Closing out bug report. Thanks!