Platform: https://racks.uninets.com
Lab Name: BIG-IP DNS
Access full BIG-IP DNS lab guide here: BIG-IP DNS Workbook
Task
• Create a zone.
• Verify zone creation with Zone Runner.
• Configure for a zone transfer.
• Use nslookup to resolve a query
Explanation:
Local BIND server configuration is managed by BIG-IP F5 DNS system ZoneRunner utility. From remote DNS servers you can create new zones or transfer current zones using F5 DNS ZoneRunner utility. Resource records contained within a zone can be added or modified. After the DNS zone exists in local BIND, you can configure the BIG-IP DNS system to answer DNS name resolution requests or zone transfers to other name servers.
This section will give you configuration details on how to transfer zones in F5 DNS.
Configuration:
Primary Zone Configuration
• Create a primary DNS zone as below
Once you are done click on Finished.
A Record Configuration
Once you are done click on Finished.
Learn How to Setup: Palo Alto – LAB Initialization for Basic Connectivity (Initial Setup Palo Alto)
Create Other A Records
Create 5 more A records using the information in the following table.
Name | TTL | IP Address |
www.uninets.com. | 30 | 10.10.17.100 |
www.uninets.com. | 30 | 10.10.17.101 |
dns2.uninets.com. | 30 | 10.10.X.54 |
mail1.uninets.com. | 30 | 10.10.X.60 |
mail2.uninets.com. | 30 | 10.10.X.61 |
NS Record Configuration
Click on Finished
MX Record Configuration
Click on Finished
CNAME Record Configuration
In order to verify the records, you have created go to DNS 8 Zones: Zone Runner: Resource Record List
Then click on Search
The above gui output will list you all the records you have created
Read this blog: Microsoft Azure Technology and How You can Get Its Training
Examine the zone database file:
Above mentioned commands will help verify the records on CLI
Verification:
Go to the management PC and take the command prompt and do the nslookup
First check the server IP address and then do the NSLOOKUP
Port Lockdown Settings
Listeners process DNS queries directed to port 53, but will not process zone transfers. Port 53, both UDP and TCP, must be open on 10.10.X.1 for a zone transfer to succeed.
Then leave rest default and click on Finished
Secondary Zone Configuration
Allow Zone Transfer from uninets1.com
Go to the uninets.com zone and allow zone-transfer to any as below
Rest leave as is and click on Update.
Now verify whether you can see the secondary zone created on not
Go to the CLI and give more /var/named/config/named.confupon doing so you may find the uninets1.com in the configuration
In between output is omitted
But still we can verify that zone is created in the CLI configuration.
To enroll in Big-IP DNS instructor-led training: visit – https://www.uninets.com/