Why DNS is essential for a working Active Directory
Operation of Active Directory requires several special entries in DNS. They are usually automatically added whenever the domain is provisioned, or a server or client joins the domain, or changes its name or IP address.
AD not only requires the normal entries that list the names and IP addresses of all servers and clients, but also an entry for the domain itself (i.e. domain.company.com, not just server.domain.company.com).
This domain entry contains several infos about the domain, for example a list of Domain Controllers that can be used to log on to the domain.
Without this info from the DNS server, the clients cannot find the Domain.
For this reason you absolutely must configure all servers and clients of the domain such that they query a DNS server that does have these special entries.
You can use either the internal DNS server that is built into the samba4 binary, or an external bind DNS server. Default is to use the internal server, and it is highly recommended that when you start using Samba4 as AD-DC for the first time, you install it this way. You can later switch between the two variants if needed. If you do use an external bind DNS server, it must use the DLZ backend and run on the Samba AD DC.
Whichever DNS server you use, you must configure the AD DC so that it uses 127.0.0.1 or its own IP address as DNS server, and all clients must be configured to use the IP address of the AD DC as DNS. This server will usually only be able to answer queries regarding servers and clients that are members of the domain. If you want your server and clients to be able to also see the rest of the world, you must configure the DNS server to forward all queries that it cannot answer itself, to another DNS server which can resolve the rest of the world.
Which DNS backend should I choose?
You should choose the DNS backend based on the requirements of your network or existing DNS installations.
The internal DNS is a new implementation, that allows you to quickly and easily setup the DNS backend that is required for every AD installation. No further work is required to set it up. Currently it covers the important and required parts for AD.
If you already having BIND running, plan complex DNS setups or you require special functions (zone transfers only from defined hosts, etc.) that are currently not supported by the internal DNS, BIND should be the preferred backend.
Your choice of a DNS backend during provisioning/upgrading is not final. If you find that your choice doesn't fit your requirements, you can flip over and change the DNS backend.
Samba Internal DNS
The internal DNS server is built into Samba and uses AD as backend. Also it is the default DNS solution when provisioning a new Samba AD DC or upgrade from a Samba NT4 domain to Samba AD. See the documentation about the Samba Internal DNS for further information.
DNS backend BIND_DLZ
BIND 9.8 and 9.9 can be setup to provide DNS resolving for zones managed in AD. They are accessable from BIND through the DLZ (dynamically loadable zones) plug-in. Please note that BIND server must run on the same machine as the Samba AD DC! See the Bind as DNS backend HowTo for further documentation.
Selecting the Forest Root Domain
See Microsofts suggestions about selecting the forest root domain: http://technet.microsoft.com/en-us/library/cc726016%28v=ws.10%29.aspx/
Avoid .local TLD
Avoid using .local as the TLD for your Active Directory. It cause connection problems with Mac and zeroconf peripherals.
See http://technet.microsoft.com/en-us/library/bb727085.aspx. Summary of the relevant parts:
- As a best practice use DNS names registered with an Internet authority in the Active Directory namespace. Only registered names are guaranteed to be globally unique. If another organization later registers the same DNS domain name, or if your organization merges with, acquires, or is acquired by other company that uses the same DNS names then the two infrastructures can never interact with one another.
- Add a prefix that is not currently in use to the registered DNS name to create a new subordinate name. For example, if your DNS root name were contoso.com then you should create an Active Directory forest root domain name such as concorp.contoso.com, where the namespace concorp.contoso.com is not already in use on the network. This new branch of the namespace will be dedicated to Active Directory and can easily be integrated with the existing DNS implementation.