Skip to main content
Skip table of contents

2575 - Creating a Primary SubZone in BloxOne DDI


The Sales department requires its own namespace in DNS. Our DNS design indicates that we are to organize the domain by logical divisions, so we decide to add a subdomain (or subzone) for the sales department as a child zone of, and we'll call it This subzone should be authoritative for and the records should show that the same administrator of the parent domain is responsible for this child domain.

Estimated Completion Time

  • 5 to 10 minutes


  • Administrative access to the CSP

  • Lab 2801: Deploying BloxOne Hosts

  • Lab 2570: Configuring DHCP Services in BloxOne DDI

  • Lab 2571: Creating DHCP Networks in BloxOne DDI

  • Lab 2573: Enabling and Configuring DNS Services

  • Lab 2574: Creating a Primary Zone in BloxOne DDI

Course References

  • 2159: BloxOne DDI Configuring DNS Services

  • 2153: BloxOne DDI Configuring DNS Zones


  1. Creating primary subzone

  2. Validating the DNS zones and records from a client

Task 1: Creating primary subzone

A subzone will need to be created under the domain in our BloxOne DDI environment, in the default view. This will be an authoritative zone so it will generate SOA and NS records automatically when we create it. The administrator will maintain this subdomain, so we can use as the administrator email contact for the zone. We will use our two DNS service instances to host this zone, Techblue DNS service 1 and Techblue DNS service 2.

Task 2: Validating the DNS  subzone and records from a client

We've created the authoritative subzone and we added some needed resource records, but we should test that this all works as designed. Using our test client, verify the response from the DNS servers and the resource records.


Task 1 Solution: Creating primary subzone

  1. With the CSP browser window, navigate to ManageDNS

  2. Select the Zones tab

  3. Click on the default DNS View to go inside the view

  4. Click on the zone to go into the zone

  5. Click the Create button, and from the drop-down select Zone and then Primary Zone

  6. Enter the zone Name: sales

  7. The FQDN below the Name field should show (note the trailing dot representing the root domain).

  8. Expand the Authoritative DNS Servers section

  9. Under DNS Authoritative Servers, click the arrow next to both of your DNS service instances to move them to the list of Authoritative DNS Servers

  10. Expand the Zone Setting Defaults section

  11. Set the Email Address (For SOA RNAME Field) to: (you will need to click the Override toggle to override the default setting)

  12. Click Save & Close

Task 2: Validating the DNS zones and records from a client

  1. On testing-linux open a Terminal window

  2. Set the IP address as a fixed address with the command sudo set-network-static-bloxone to allow a route to the DNS server.

  3. Check the dig responses for the following queries. All queries should return Authoritative Answers (aa) with NOERROR:

    dig @ soa

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.