The VergeCloud DNS Load Balancer provides an intelligent and scalable way to distribute incoming traffic across multiple origin servers linked to your domain or subdomains. By choosing the appropriate load balancing method such as Round Robin, Weighted, or Geo-based routing, you ensure high availability, optimized performance, and better resilience for your applications.
DNS-level load balancing serves as the first layer of redundancy. Instead of routing all users to a single origin, the DNS system returns multiple healthy servers, minimizing downtime and reducing bottlenecks. This approach is especially effective for large-scale platforms, globally distributed applications, and environments that require high availability through
multi cloud load balancing.
Preparing Your Domain and Origins for VergeCloud DNS Load Balancing
Before enabling DNS load balancing in VergeCloud, ensure the following prerequisites are met:
- Your domain is already added and verified in the VergeCloud dashboard
- DNS management for the domain is handled by VergeCloud
- You have two or more origin server IP addresses available
- Each origin server is reachable and properly configured to serve traffic
- TTL values are set appropriately to allow faster DNS updates if needed
Preparing your infrastructure in advance ensures smooth configuration and avoids traffic disruption during setup.
What is a DNS Load Balancer?
A DNS Load Balancer distributes DNS responses for a domain or subdomain among multiple IP addresses pointing to your origin servers. When a user queries your domain, the DNS server returns one or more IPs based on the selected routing method. This ensures that traffic flows across available servers in the most efficient manner.
Steps to Enable DNS Load Balancing on VergeCloud
Follow these steps to configure DNS load balancing from the VergeCloud control panel:
1. Log in to the VergeCloud Dashboard
Select the domain where you want to enable DNS load balancing.
2. Open the DNS Records Section
Navigate to DNS → Records and click Add Record.
3. Create an A or AAAA Record
Choose A Record for IPv4
Choose AAAA Record for IPv6
4. Enter the Hostname
Use @ for the root domain
Or specify a subdomain (e.g., app, api)
5. Add Origin IP Addresses
Enter the IP address of each origin server
Click Add New Value to include multiple origins
6. Select the Response Type
Choose whether DNS returns a single IP or multiple IPs
Multiple responses improve redundancy and availability
7. Choose a Load Balancing Method
Round Robin – Distributes traffic evenly
Weighted Distribution – Sends more traffic to higher-capacity servers
Geographic Load Balancing – Routes users to the nearest server location
8. Save the Configuration
Once saved, DNS load balancing becomes active based on TTL settings.
Key Fields for Configuring DNS Load Balancing in VergeCloud
Name
Specifies the hostname or subdomain where load balancing applies.
Use @ for the root domain or enter a specific subdomain.
Value
Contains the IP addresses of your origin servers.
Multiple values enable traffic distribution.
Response Type
Determines whether DNS returns one or multiple IP addresses per query.
Multiple responses improve fault tolerance and uptime.
Load Balancing Method
Controls how traffic is distributed:
Round Robin – Equal distribution
Weighted – Priority-based routing
Geographic – Region-aware routing
Weight Configuration
Defines how much traffic each server receives.
Only the ratio matters (e.g., 1:2 behaves the same as 10:20).
Geographic Load Balancing
Routes users to the closest server based on location, improving latency and user experience—ideal for global and multi cloud load balancing deployments.
Testing DNS Load Balancer Configuration on VergeCloud
After configuring your DNS Load Balancer, it is essential to test the setup and confirm that DNS queries return the expected results.
Use the dig command:
dig A example.com
Sample Output
; <<>> DiG 9.16.1-Ubuntu <<>> A example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12345
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;example.com. IN A
;; ANSWER SECTION:
example.com. 120 IN A 192.168.1.1
example.com. 120 IN A 192.168.1.2
example.com. 120 IN A 192.168.1.3
;; Query time: 27 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Sep 26 15:10:12 UTC 2024
;; MSG SIZE rcvd: 100
The multiple IP addresses shown in the ANSWER SECTION indicate that load balancing has been applied correctly.
Operational Considerations for VergeCloud DNS Load Balancing
1. Use Weighted Distribution for Uneven Capacity
If servers have different performance capabilities, assign higher weights to stronger origins for efficient traffic handling.
2. Enable Geo Load Balancing for Global Users
Routing users to the nearest server improves performance and reduces latency—ideal for international traffic.
3. Allow for DNS Propagation
DNS changes may take up to 24–48 hours to fully propagate, depending on TTL values and ISP caching behavior.
4. Monitor Availability
Regularly check origin health to ensure uninterrupted traffic flow.
FAQ
1. Does VergeCloud support multi cloud load balancing?
Yes. VergeCloud DNS Load Balancing works seamlessly across multiple cloud providers, allowing true multi cloud load balancing for high availability and disaster recovery.
2. Can I use DNS load balancing without a CDN?
Yes. DNS load balancing operates independently and can be used even without CDN acceleration.
3. How long does DNS load balancing take to activate?
Changes usually apply within minutes but may take up to 48 hours depending on TTL and ISP caching.
4. Is DNS load balancing suitable for failover?
Yes. It provides an effective first layer of failover by distributing traffic across healthy origins.
5. Does VergeCloud provide support for DNS configuration?
Yes. VergeCloud offers
24/7 cloud support to assist with DNS configuration, troubleshooting, and optimization.