Difference between revisions of "The Samba AD DNS Back Ends"
m (/* remove unsupported dns backend from list of supported dns backends)
m (/* minor update)
|Line 37:||Line 37:|
| type = important
| type = important
| text = Do not use the <code>BIND9_FLATFILE</code> DNS back end. It is not supported and will be removed
| text = Do not use the <code>BIND9_FLATFILE</code> DNS back end. It is not supported and will be removed .
Latest revision as of 12:30, 28 August 2019
In an Active Directory (AD), DNS is a very important service. It is used for:
- name resolution
- locating services, such as Kerberos and LDAP
- locating local domain controllers (DC) when using AD sites. For details, see Active Directory Sites.
|All clients and server in an AD must use a DNS server that is able to resolve the AD DNS zones.|
Supported DNS Back Ends
Samba supports the following DNS back ends:
- Default when provisioning a new domain, joining an existing domain or migrating an NT4 domain to AD.
- No additional software or DNS knowledge is required.
- Use this back end for simple DNS setups. For a list of limitations, see Limitations.
- Requires BIND 9.8 or later installed and configured locally on the Samba Active Directory (AD) domain controller (DC). For additional information, see Setting up a BIND DNS Server.
- Requires knowledge about the BIND DNS server and how to configure the service.
- Use this back end for complex DNS scenarios, you can not configure in the internal DNS.
If you are unsure which DNS back end to select during the DC installation, start with the Samba internal DNS. You can change the back end at any time. For details, see Changing the DNS Back End of a Samba AD DC.
|Do not use the |
Selecting the AD Forest Root Domain
Before you provision your Active Directory (AD), you must select a DNS zone for your AD forest root domain. For details, see Active Directory Naming FAQ.
|Samba does not support renaming the AD forest root domain.|
- Use a domain name you own.
- Use a subdomain of your domain, such as
- Do not use
.localdomains. They can cause problems with Mac OS X and Zeroconf.
For details, see Active Directory Naming FAQ.