Load Balancing your DNS

Configuration has yet to be fully verified, Kemp Support will gladly assist if your DNS traffic is not flowing as expected.

 

1   Introduction

 
DNS Servers. Domain name system servers match domain names like Kemptechnologies.com to their associated IP addresses — 107.22.236.183 . When you type kemptechnologies.com into your web browser's address bar, your computer contacts your current DNS server and asks what IP address is associated with kemptechnologies.com.

 

1.1  Document Purpose

This section details a configuration for a specific application that has been provided by a customer but has yet to be fully tested.

This specific configuration will ensure that your DNS servers are highly-available, scalable, and secure.

Configuration has yet to be fully verified, Kemp Support will gladly assist if your DNS traffic is not flowing as expected.

 

2  Configuration Required

  

2.1  Global Configuration

       No Changes Required

 

2.2  Virtual Service Configuration: 

In most scenarios only one UDP port 53 Virtual Service will be required to Load Balance your DNS queries. You can also configure a TCP port 53 service, which will be used to Load Balance DNS Zone Transfer Files. 

 

 2.3    DNS UDP 

      > New Virtual Service

      > Enter IP Address

      > Port = 53

      > Name = DNS UDP

      > Protocol = UDP

      > Add New Virtual Service



2.4       Standard Options   

      >   Disable Transparency

      >  Persistence = None

      > Scheduling Method = Round Robin

      > Idle Connection Timeout = 3 Seconds

 

 

2.5    Real Servers

      > Checker Parameter Type = Name Service (DNS) Protocol

      > Add New 

      > Enter Real Server IP Address

      > Port = 53

      > Forwarding Method = NAT

 

 

3.0    DNS TCP

      > New Virtual Service

      > Enter IP Address

      > Port = 53

      > Name = DNS TCP

      > Protocol = TCP

      > Add New Virtual Service



3.1       Standard Options   

      >   Disable Transparency

      >  Persistence = None

      > Scheduling Method = Round Robin

      > Idle Connection Timeout = 180 Seconds

 



3.2    Real Servers

      > Checker Parameter Type = Name Service (DNS) Protocol

      > Add New 

      > Enter Real Server IP Address

      > Port = 53

      > Forwarding Method = NAT

 

 

If you have successfully Load Balanced your DNS environment by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you

 

 

2

4 comments

Avatar

strzebia

First, thank you for the post.  I have a couple suggestions.  TCP is used for responses over a packet in length in addition to DNS zone transfers.  I suggest DNS UDP and DNS TCP for names.  Also, the numbering restarts after the UDP section ends.  Finally. in UDP 2.3, the name is TFTP not DNS UDP.  Hope this helps.

1

Avatar

Darren Morrissey

Thanks for the suggestions, changes made

0

Avatar

micheleharris725

Thank you for updating us with the outcome.

 

walgreenslistens

0

Avatar

Nam Pham Van

Thansks for all, does our solution support DNS AnyCast deployment?

 

0

Please to leave a comment.

Didn't find what you were looking for?