2575 - Creating a Primary SubZone in BloxOne DDI
Cloud Services Portal (CSP) is now Infoblox Portal
In early September, Cloud Services Portal (CSP) became Infoblox Portal with a new look-and-feel, and a new URL (https://portal.infoblox.com). As a result of this change, the layout and organization of several menus have been updated.
Unfortunately, this means that our video courseware and lab guides no longer match the new user interface. However, we are currently in the process of updating them, and they should be ready soon.
In the meantime, we have some resources to help you navigate the new interface:
We have created a mapping of the previous menu locations and their new breadcrumb location.
Additionally, you can find a walkthrough video of the new User Interface on Launchpad.
We apologize for any inconvenience this may cause and kindly ask for your patience as we work through this transition.
Scenario
The Sales department requires its own namespace in DNS. Our DNS design indicates that we are to organize the techblue.net domain by logical divisions, so we decide to add a subdomain (or subzone) for the sales department as a child zone of techblue.net, and we'll call it sales.techblue.net. This subzone should be authoritative for sales.techblue.net 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
Prerequisites
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
Tasks
Creating primary subzone sales.techblue.net
Validating the DNS zones and records from a client
Task 1: Creating primary subzone sales.techblue.net
A subzone sales.techblue.net will need to be created under the techblue.net 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 techblue.net administrator will maintain this subdomain, so we can use admin@techblue.net 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 sales.techblue.net 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.
Solutions
Task 1 Solution: Creating primary subzone sales.techblue.net
With the CSP browser window, navigate to Manage → DNS
Select the Zones tab
Click on the default DNS View to go inside the view
Click on the zone techblue.net to go into the zone
Click the Create button, and from the drop-down select Zone and then Primary Zone
Enter the zone Name: sales
The FQDN below the Name field should show sales.techblue.net. (note the trailing dot representing the root domain).
Expand the Authoritative DNS Servers section
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
Expand the Zone Setting Defaults section
Set the Email Address (For SOA RNAME Field) to: admin@techblue.net (you will need to click the Override toggle to override the default setting)
Click Save & Close
Task 2: Validating the DNS zones and records from a client
On testing-linux open a Terminal window
Set the IP address as a fixed address with the command
sudo set-network-static-bloxoneto allow a route to the DNS server.Check the dig responses for the following queries. All queries should return Authoritative Answers (aa) with NOERROR:
dig @10.100.0.110 sales.techblue.net soa