Bug 7634 - DNS registration problems
Summary: DNS registration problems
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 4.0.6
Hardware: Other Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Michael Adam
QA Contact: Samba QA Contact
Depends on:
Reported: 2010-08-20 04:48 UTC by David Woodhouse
Modified: 2014-07-24 08:09 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description David Woodhouse 2010-08-20 04:48:42 UTC
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.
Comment 1 Björn Jacke 2014-07-24 08:09:03 UTC
how does it work with "bind interfaces only = yes" for you?