B
B
Bermut2021-07-07 01:06:00
Domain Name System
Bermut, 2021-07-07 01:06:00

How are dns servers arranged?

The question is purely out of curiosity, how the dns servers are arranged from the technical side, for example Google DNS, as I see it, there is a request for ip - 8.8.8.8, on port 53, and the server sends a response from the ip of the domain, this is understandable, but as I it seems that no matter how powerful one node is, it is not capable of processing such a number of requests per second, so, in fact, the question itself is - how is the distribution of requests, traffic, from one ip, from one port, to several servers?

Answer the question

In order to leave comments, you need to log in

6 answer(s)
A
Alexey Cheremisin, 2021-07-07
@leahch

Without touching DNS, but in general.
One IP address can hide a whole factory of servers, sometimes hundreds of them.
An approximate example is masquerading with an IP address on routers and smart switches in the networks of providers, companies, and even apartments. Almost any home router can masquerade IP addresses. If we add here distribution and load balancing, and query caching (already regarding DNS) on intermediate servers, then it is quite possible to live in such a distributed system.

D
Drno, 2021-07-07
@Drno

https://ru.wikipedia.org/wiki/Round_robin_DNS The request comes to one ip address, then it is proxied
to different DNS servers for a response (usually freer)
single site servers

V
ValdikSS, 2021-07-11
@ValdikSS

1. There can be several servers behind one IP address, to which requests are distributed to distribute the load.
2. One IP address can be globally routed to different physical locations, depending on the region and/or provider. This is called anycast .

A
aquariussanya, 2021-07-07
@aquariussanya

"... no matter how powerful one node is, it is not capable of processing such a number of requests per second ..."
There is a cache for this, it caches OS requests, a router, a provider's DNS, and so on. Like so

V
Vladimir Pilipchuk, 2021-08-05
@SLIDERWEB

The architecture may be different. Judging by the answers of the eights, there is a whole farm there.
I also have my own recursor. It holds zones and resolves the entire "internet" for infrastructure. There are a lot of requests.
I did this:
There are 2 hardware balancers at the input. All requests for DNS ports are sent to 4 Unbound-based resolvers, which forward requests that are not answered in the local cache to 4 DNS servers behind each.
Balancers evenly distribute requests to 4 resolvers, resolvers, in turn, equally distribute requests to 16 servers.
Something like this.
Total: 16 DNS servers are hidden behind 4 resolvers behind two balancers.
I think this is done by many hosters, registrars and companies that receive a lot of traffic.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question