BIG-IP F5 DNS Services: Resolving Queries using Local BIND with ZoneRunner on F5 DNS

Lab Name: BIG-IP DNS
Access the full BIG-IP DNS Lab Guide here: BIG-IPDN Workbook

This article will provide a detailed overview of “Resolving Queries using Local BIND with ZoneRunner on F5 DNS”
Task* Create a new zone. * Verify the zone creation with Zone Runner. * Configure for a transfer of a zone.
BIG-IP F5DNS system ZoneRunner utility manages local BIND server configuration. F5 DNS ZoneRunner utility can be used to transfer existing zones and create new ones from remote DNS servers. You can add or modify resource records within a zone. Once the DNS zone is created in local BIND you can configure BIG-IP DNS to respond to DNS name resolution requests and zone transfers to other nameservers.
This section will provide configuration details for how to transfer F5 DNS zones.
Configuration:Primary Zone Configuration* Create a primary DNS zone as below

After you’re done, click on Finished.

A Record Configuration
Make an A record following the diagram.

After you’re done, click on Finished.

Learn How to Setup Palo Alto – Basic Connectivity LAB Initialization (Initial Setup Palo Alto).

Other A Records
Use the following information to create 5 additional A records.
NS Record Configuration
Below, create an NS record

Click on Finished

Configuration of MX Record
Below, create a MX record

Click on Finished

Configuration of CNAME Records
As below, create a CNAME Record

To verify the records you have created, go to DNS 8 zones: Zone Runner: Resource record List

Next, click on Search

The gui output above will list all records you have created

This blog explains Microsoft Azure Technology and how you can get it’s training.

Check out the zone database file.
Cd /var/named/config/namedb
The commands above will verify records on CLI.

Take the command prompt to the management PC, and then do the nslookup

First, check the server IP address. Next, do the NSLOOKUP
Port Lockdown Settings
Listeners will process DNS queries directed at port 53 but not zone transfers. To allow a zone transfer to occur, port 53, both UDP/TCP, must be available on 10.10.X.1.
Modify your BIG-IP DNS system’s self IP address 10.X.1 to allow zone transfers via UDP port 53 or TCP 53.

Next, click on Finished and leave the default state of rest.

Configuration of Secondary Zone
As below, create a Secondary DNS zone

Zone Transfer available from
Zone transfers from are allowed as follows

Go to and allow zone-transfers to any of the below

Don’t worry, just leave it as it is and click on “Update”.
Now, verify that you can see the secondary area created on not

Go to the CLI and give more /var/named/config/named.confupon doing so you may find the in the configuration

The in-between output is omitted
We can still verify that the CLI configuration has created a zone.
To enroll in Big-IP DNS instructor-led training: visit –