Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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, host, or an IP address that can resolve queries for the zone. You can also assign one or more external DNS servers as default forwarders for a forward zone. For example, define a forward zone so that the application forwards queries about a partner’s internal site to a DNS server, which the partner hosts, configured just for other partners to access. For more information on DNS Zones, see Configuring DNS Zones

Note

The use of a forward zone is different from that of a forwarder. A forwarder is a DNS server that performs recursive lookups on behalf of the DNS servers that forward queries to it. For more information, see Using Forwarders in Global DNS Configuration.

BloxOne DDI forwards queries to the DNS server of a forward zone, because the DNS server can resolve queries for the zone. The application forwards queries to a forwarder regardless of zones.

To create a forward zone, complete the following:

  1. From the Cloud Services Portal, click Manage -> DNS -> Zones.
  2. Create a DNS view or click an existing DNS view. For more information about creating a DNS view, see Configuring DNS Views.
  3. On the Zones page, click Create and choose Forward Zone from the drop-down list.
  4. On the Create Forward Zone page, specify the following:
    • Name: Enter the domain name for the zone. 

      • To create an IPv4 reverse-mapping zone, specify in-addr.arpa as the top-level reverse-mapping zone while specifying a name for the zone.

      • To create an IPv6 reverse-mapping zone, specify ip6.arpa as the top-level reverse-mapping zone while specifying a name for the zone.

    • Description: Enter a descriptive comment about the zone.
    • Disable for DNS Protocol: Click this check box to temporarily disable this zone. For information, see Enabling and Disabling Zones.
    • Use Forwarders Only: Select the check box if you want the application to query forwarders only (not root servers) to resolve domain names in the zone.
    • DNS SERVERS: Define DNS servers for the zone. Choose one or more hosts from the available list. The host that you choose serves the zone. For more information about hosts, see Configuring Hosts. You can also define zones without assigning DNS name servers to them. This is particularly helpful during pre-deployment provisioning and during troubleshooting activities. 
    • FORWARDERS: Define forwarders for the zone. You can choose to forward queries to an external IP address, a host, or a DNS server group:
      • Forward to Address: Choose an external IP address to which you want to forward the queries.
      • Forward to Host: Choose a host from the drop-down list. The queries against the zone are forwarded to this host. For more information about hosts, see Configuring Hosts.
      • DNS Server Group: Choose a DNS server group from the drop-down list to forward the queries to a set of DNS servers.
    • Tags: Click Add to associate keys with the forward-mapping zone and specify the following details:

      • KEY: Enter a meaningful name for the key, such as a location or a department.  

      • VALUE: Enter a value for the key.    

      To remove a tag, select the respective check box and click Remove to delete the associated tag. For information about tags, see Managing Tags.

  5. Define DNS server groups for the zone. Choose either DNS Server Group, External Primary, or Internal Secondary from the list. For information on specifying authoritative DNS server groups, see Configuring DNS Server GroupsYou can also define zones without assigning DNS server groups to them. This is particularly helpful during pre-deployment provisioning and during troubleshooting activities. 
  6. Click Save & Close to save.

Warning

The subdomains starting with ns.b1ddi and b1ddi are reserved and cannot be used as a prefix for the names of zones and resource records.

  • No labels