DNS zones are organized within a DNS View. From the Cloud Services Portal, click Manage -> DNS -> Zones. All existing views are shown under All DNS Views. If there are multiple views, you must click the particular DNS view to drill down to view the zones and subzones. If there are no DNS views, you must create them before adding a zone. For more information about creating a DNS view, see Configuring DNS Views.
You can delegate a zone to an Authoritative DNS Server. DNS requests made to the delegated zone are serviced by the Authoritative DNS Server to which the zone is delegated. For more information about creating a zone delegation, see Configuring Zone Delegation.
To view the list of DNS zones, complete the following:
From the Cloud Services Portal, click Manage -> DNS.
- Click the respective DNS view.
- The application displays the following information:
- NAME: The name of the zone.
- DNS NAME: The DNS name of the zone.
- TYPE: Type of zone, whether a primary, secondary, or forward zone.
- DESCRIPTION: Additional information about the zone.
You can also perform the following in this tab:
- Click to reorder the columns or to select the columns to be displayed.
Click -> Edit or select the check box for the respective record and click Edit to modify a zone.
Select a zone to view the additional details. If you do not want to view the details in the right panel, click .
Click to view the zone details or click to view the details in a tabular format.
Enter the value that you want to search in the Search text box. BloxOne DDI displays the list of records matching the keyword in the text box.
Click to filter the objects by name and description.
- Click -> Move to Recycle Bin to move the object to the recycle bin. You can restore the object later or delete it permanently as required. For more information, see Recycle Bin.
A primary zone stores the master copy of the zone data. A secondary zone is a read-only copy of the primary zone that is stored on a different server. The secondary zone cannot process updates and can only retrieve updates from the primary zone. The secondary zone can answer DNS name resolution queries from client nodes, which helps reduce the workload on the primary zone. When you want to forward queries for data in a particular zone, define the zone as a forward zone and specify one or more DNS servers, an on-premise host, or an IP address that can resolve queries for the zone.
An authoritative zone is a zone for which the local server references its own data when responding to queries. The local server is authoritative for the data in this zone and responds to queries for this data without referencing another server. Primary and secondary zones are authoritative zones. A forward zone is not an authoritative zone.
A primary zone on BloxOne DDI (cloud) is an authoritative zone.
The following are two types of authoritative zones:
- Forward-mapping: An authoritative forward-mapping zone is an area of domain name space for which one or more name servers have the responsibility to respond authoritatively to name-to-address queries.
Reverse-mapping: A reverse-mapping zone is an area of network space for which one or more name servers have the responsibility to respond to address-to-name queries.
You can configure and manage authoritative forward-mapping and IPv4 reverse-mapping zones on the Infoblox BloxOne DDI cloud service portal. When you create an authoritative forward-mapping zone or reverse-mapping zone, you assign zone authority to a DNS server and define it as the primary server for the zone. A primary server is designated as the primary source for the zone and maintains a master copy of the zone data.
You can also create one or more secondary DNS servers for a zone. A secondary server for a zone receives read-only zone data from the primary server. If a zone is part of an internal DNS structure for a private network, the inclusion of a secondary DNS server is optional, though highly recommended. If a zone is a part of an external DNS structure for a public network such as the Internet, then a secondary server in a different subnet from the primary server is required. This requirement provides an additional safeguard against localized network failures causing both primary and secondary DNS servers for a zone to become inaccessible.
You can specify the primary and secondary server for a zone or you can specify a DNS server group. A DNS server group is a collection of one or more primary servers and one or more secondary servers. For information on DNS server groups, see Configuring DNS Server Groups.
The following is an example of an IPv4 reverse-mapping zone hierarchy:
You can perform the following actions:
This page has no comments.