If you're running Samba as Active Directory Domain Controller, you also have to administer a DNS server.You will already find general information on the internal DNS and the BIND DLZ module and documentation about Bind as DNS Backend in the Wiki.

dynamically updating a zone-24dynamically updating a zone-43

By default, Samba creates the following two forward zones during provisioning/upgrading (of course with your own domain name): The Samba internal DNS is a new implementation.

Although BIND is a grown up DNS and long in production on millions of servers, the Samba BIND DLZ module is still new.

Well, I will also offer the nitty gritty below the summary for those who want to read. But DHCP will register its PTR (reverse entry) record.

Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.

The third: 192.168.0.0/16 will allow you to have a maximum of 65,534 ipaddresses.

You can, if you so wish, use different Subnet masks/CIDRs to split up the RFC1918 zones.For instance, using 192.168.0.0/24 (netmask 255.255.255.0) will you allow you to have a maximum of 254 [email protected] SOA \ "dc1.samdom.hostmaster.63 90 3600" \ "dc1.samdom.admin.64 90 3600" Password for [[email protected] COM]: Record updated successfully To administer DNS from a Windows client, you have to install the DNS MMC Snap-In.That's why both backends don't yet cover all the features that you can setup with the Microsoft DNS tools.If you discover problems or missing features, please open a bug report/feature request at https://bugzilla.samba.org/.This means that any authenticated user or computer can create a new object in the zone.