The following table displays the zone types supported by DDI orchestrator:
| Type | Description |
|---|---|
| Primary | A primary zone, which is always the original copy of the zone and is always present on that zone’s primary server. |
| Dynamic | A dynamic primary zone, which is always the original copy of the zone and is always present on that zone’s primary server. |
| AD integrated | An Active Directory-integrated primary zone. |
| Secondary | A read-only copy of a primary zone or another secondary zone. |
| Hint | Root zone used for bootstrapping of recursive DNS servers. |
| Private | A private zone within a cloud environment, which is not exposed to the public internet. Specific to AWS and Azure. |
| Include | A BIND-specific zone containing DNS resource records that can be included in other zones. |
Configuration types: The following zone types are configurations that tell the
(recursive) DNS server how to resolve zones it cannot resolve as it typically
does.
| Type | Description |
|---|---|
| Stub | A stub zone is a copy of a DNS zone that contains only resource records that identify the authoritative DNS servers for that zone. A stub zone is dynamically updated from the list of primary DNS servers. |
| Static-stub | A BIND-specific zone type to configure conditional forwarding, similar to Stub but is static, meaning it has a set of preconfigured NS entries. |
| Forward | A forward zone contains a list of name server addresses, called forwarders, that can resolve queries for the zone. With forward zones, queries are forced to go to the specified addresses. |
| Response policy (RPZ) | A response policy zone contains a list of harmful domains that need to be blocked or redirected. The configured response policy determines how DNS resolvers response to queries to these domains, for example, blocking or redirecting the query to a different domain. Specific to BIND or MDDS. |
Static vs. Dynamic zones
Dynamic zones can use dynamic DNS updates to update their resource records. Due to the nature of dynamic zones, DDI orchestrator handles them differently from static zones.
While the zone content in static zones is read from a disk on the server, dynamic zone
content is retrieved from the server via zone transfer. When setting up a dynamic zone,
make sure that zone transfers are allowed to localhost.
Note: Dynamic zones are applicable to BIND and Microsoft DNS servers.
To change a zone's type from static to dynamic, edit the zone options.
- Locate the zone in the list on the DNS page.
- Use either the Action or ellipses in the row to select Edit zone options.
- Either use the dropdown to select Update restrictions or, if there is already an update restriction defined, use the + Add button to add a new one.
- Set the update restrictions to anything other than Allow: None.
- Select Save.
The following table provides a comparison of how you can manage static and dynamic zones in DDI orchestrator:
| Objects | Static zones | Dynamic zones |
|---|---|---|
| Records |
|
|
| TTL (Time-To-Live) |
|
|
| Comments |
|
|