samba - Oct 2014 - Samba internal DNS + 2nd DNS

I'm workign to setup Samba4 and my current centos server deployment uses
TinyDNS/DNSCache for the DNS.  Understanding that it is best to use Sambas
internal DNS for AD, I'm wondering how others are doing DNS?  I really
don't want to use BIND.

Should my DHCP server send ddns updates to Samba's internal DNS for client
leases?

Thanks,

-- 
Greg J. Zartman
Board Member

Koozali Foundation, Inc.
2755 19th Street SE
Salem, Oregon 97302
Cell:  541-5218449

SME Server user and community member since 2000

Greg Zartman writes:
> I'm workign to setup Samba4 and my current centos server deployment
uses
> TinyDNS/DNSCache for the DNS.  Understanding that it is best to use Sambas
> internal DNS for AD, I'm wondering how others are doing DNS?  I really
> don't want to use BIND.
We're not yet in production with Samba 4, but in our test systems, we do it
like this:

- Samba listens on localhost and the LAN interface, port 53.
- dnscache listens on 127.0.0.2 port 53.
- tinydns listens on 127.0.0.3 port 53.

Samba has the dnscache instance as DNS forwarder.
Additional domains can be managed either in Samba, or in tinydns.

/etc/samba/smb.conf snippet:
  interfaces = 192.168.1.1/24 127.255.255.255/8
  bind interfaces only = Yes
  hosts allow = 192.168.1.0/255.255.255.0 127.0.0.1 LOCAL/unixdom
  dns forwarder = 127.0.0.2

# netstat -plunt | grep :53
tcp  0 0  127.0.0.1:53     0.0.0.0:*  LISTEN   3974/samba
tcp  0 0  192.168.1.1:53   0.0.0.0:*  LISTEN   3974/samba
tcp  0 0  127.0.0.2:53     0.0.0.0:*  LISTEN   1839/dnscache
udp  0 0  127.0.0.1:53     0.0.0.0:*           3974/samba
udp  0 0  192.168.1.1:53   0.0.0.0:*           3974/samba
udp  0 0  127.0.0.2:53     0.0.0.0:*           1839/dnscache
udp  0 0  127.0.0.3:53     0.0.0.0:*           1842/tinydns

Regards,

Roel