[Samba] After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command

Rowland Penny rowlandpenny241155 at gmail.com
Wed Dec 2 16:39:40 UTC 2015

On 02/12/15 15:34, Jonathan S. Fisher wrote:
> Dnsmasq is not running locally! Disabling it would do nothing but stop DHCP
> and DNS forwarding for 2000+ soon to be irate people.

There is nothing wrong with dnsmasq, it just has no place in a AD domain.

Your AD domain should probably separate from your regular domain i.e. 
something like 'internal.your.domain'
Your AD DC should be running a dns server, and forwarding to the dnsmasq 
machine for anything outside the AD domain.
Your client needs to be using 'internal.your.domain' as its domain, it 
also needs to be using the DC as its only DC, unless you have more than 
one DC, in which case you can use all your DCs as name servers.

If you follow the Samba wiki, it will work, if it doesn't, then it is 
probably down to your network.


> What I am going to do however is bypass DHCP completely and assign a static
> address with DNS pointed straight at active directory. If that still
> doesn't work, I think I can definitely narrow this down to a bug in Active
> Directory, our AD configuration, or a bug in Samba.

More information about the samba mailing list