Understanding DNS Load Balancing and Its Role in Modern Architecture

Hello, I am a senior architect.

Limitations of traditional approaches

How CDN works

The magical SOA (explanation authority) mechanism

Basic principles of DNS load balancing

Summary

When a website’s traffic grows, load balancing becomes a basic skill for any architect, similar to the essential role of performance in a comedy act.

Limitations of Traditional Approaches

Traditional load balancing is single‑point, whether hardware or software, as shown in the diagram below. For most needs this simple architecture works and is easy to maintain, which is why many companies use it.

However, the response speed of a site is limited by the capacity of the load‑balancing node, and if that node fails the whole site goes down. Horizontal scaling of backend services helps, but each node still has hardware limits and does not follow the evolution of internet technology.

How CDN Works

CDN, as a major internet infrastructure, solves traffic distribution by spreading user requests across many edge nodes, as illustrated in the following diagram.

Requests are no longer concentrated on a single node; they are distributed to suitable nodes, so a single point of failure only affects a portion of users, and additional fail‑over mechanisms can be applied.

The same idea can be applied to a traditional BS architecture by routing user requests directly to different servers instead of a single central node.

What Is DNS?

DNS is the system that translates domain names to IP addresses. Most people use DNS daily without knowing its fundamentals.

DNS is a tree‑structured distributed network. A DNS cache server reduces the load on the global DNS system. If a request misses the cache, the server performs a standard recursive query, starting from the root server.

The root server holds the ultimate authority for all domain names, but it does not return the final answer directly; instead, it points to the next level of authoritative servers.

SOA (Start of Authority) Mechanism

The root server delegates the query to the appropriate authoritative server, which then provides the answer. This delegation reduces the load on the root servers.

Basic Principles of DNS Load Balancing

From the above process we conclude that DNS is a reliable, distributed network and that its final resolution can be controlled. By manipulating the DNS response, we can return different server IPs according to a defined frequency, achieving load balancing, geographic routing, or fail‑over.

DNS Service Providers Supporting Load Balancing

AWS Route 53

NSONE

Dyn

dnspod

We are already using AWS Route 53 and dnspod with good results.

Summary

DNS can be used for many advanced scenarios beyond simple name resolution, such as fail‑over, geographic routing, and load balancing. As internet usage evolves, these techniques will become increasingly important.

For further reading, see the linked articles and resources.