I've noticed that 'net join' will register the host in DNS. Useful...
However, it only works if I've already *added* the fully qualified host name to my /etc/hosts file. Is there any *other* way that it could infer the DNS domain name to use?
Also, it's registering the wrong addresses. Firstly, it doesn't seem to be registering IPv6 addresses; only Legacy IP.
And it's registering *every* Legacy IP address on the system, *except* for the one I wanted it to -- the VPN address.
I added 'interfaces = lo vpn0' to smb.conf, in the hope that it would *only* add the IP address of the VPN interface which connects me to the company network -- but then it just says 'DNS update failed!'. Presumably because it doesn't like the tun device for some reason?
Also, does winbindd repeat the DNS setting? I have a dynamic IP on the VPN, so when I reconnect to the VPN and winbindd manages to rejoin the domain, it should hopefully be updating the DNS?
Probably some user error in the above, but potentially 3 or 4 minor bugs/feature requests related to DNS too.
how does it work with "bind interfaces only = yes" for you?
those are multiple bug reports in one and the bug report summary is very generic, this is not good.
DONE: you don't need to add the fqdn to /etc/hosts as current versions now use the configured realm to construct the fqdn for dns registration
DONE: ipv6 address registration is working in current versions
DONE: not every leagace IP is being registered if you limit it by using "interfaces" paramter
REDIRECT: for repeated DNS registration updates, goto bug 8894
OPEN: the vpn interface IP is not being registered, probably because the interface is not broadcast capable, I thnk the check for broadcast capability is most of the time not good, just for good old nmbd maybe it was.