Configuring ISC BIND Support
| Table of Contents |
|---|
Getting Started
...
| title | BIND Version Compatibility |
|---|
BIND 9 Support is officially supported. Please note that as of May 24, 2018, ISC implemented a different release numbering scheme. See https://kb.isc.org/docs/aa-00896 for information on ISC's Software Support Policy and Version Numbering.
Previously new feature development releases were tagged as "alpha" and "beta", leading up to the first stable release for a given development branch, which always ended in ".0".
Now, however, BIND has adopted the "odd-unstable/even-stable" release numbering convention. There will be no "alpha" or "beta" releases in the 9.13 branch, only increasing version numbers. So, for example, what would previously have been called 9.13.0a1, 9.13.0a2, 9.13.0b1, and so on, will instead be called 9.13.0, 9.13.1, 9.13.2, etc.
...
- Before you Begin
Before configuring ISC BIND in ProVision, we recommend verifying server permissions for the user:
- You will need a user who can log in to the DNS server and make changes to the directory in which the zones are being stored
...
- Additionally, it is
...
- useful for this user to have the ability to restart the DNS server
...
- The login and password for this user will be required to configure this server on the DNS Admin page
Zone File Overview
ProVision .6connect Zone files are written out in the following format:
| Code Block | ||
|---|---|---|
| ||
/path/to/zone/directory/viewName/zoneFirstLetter/zonefile.zone |
If no views are configured, or if views are expressly disabled, then the default viewName "6connectGeneric" is used. The zoneFirstLetter is the first letter of the zone name, so the subdirectory 'microsoft.com.zone' is placed in would be /m/.
All 6connectProVision-managed Zones are managed by a dedicated 6connect configuration file named 6connect_named.conf. This file is created to act a supplementary conf file to work in concert with any existing named.conf which might exist. To include the 6connect configuration the configuration file, edit named.conf and append the following line:
| Code Block |
|---|
include "/path/to/conf/directory/6connect_named.conf"; |
You must remember to include the 6connect ProVision configuration file or none of the changes managed by ProVision will take effect!
| Note | ||
|---|---|---|
| ||
| It is also important to note that if your existing named.conf file contains zones within Split Horizon views, then the |
...
| ProVision-managed zones must also be view-enabled. Likewise, if existing zones are not grouped into views, then views must be disabled on ProVision. |
Adding a BIND Server
To create a new server, start from the DNS Tab, select the DNS Servers sub menu. Then, click the "Add Server" button next to "DNS Server List".
...
After entering the server-specific settings in this section, you can click the "Test Connection" button at the bottom right of the page to test the server connection and authentication.
A window will pop up showing a success or failure response.
...
The new server will now be added to the DNS Servers list. These settings may be changed at any time by selecting the server from the server list and editing the information.
Additional Information
For additional information on working in DNS, see the following sections:
...