DNS, the Domain Name System, turns a name like example.com into the IP address your computer connects to. Almost every page load and API call starts with a DNS lookup, so when DNS goes wrong, everything that relies on a name goes wrong with it.
Why names need looking up
Computers on the internet reach each other by IP address, such as 203.0.113.10. People remember names. DNS is the directory between the two, and it is spread across many servers rather than kept in one place. Because the name is looked up each time, a site can move to a new server while visitors keep typing the same name.
How a lookup works
Your computer hands the lookup to a recursive resolver, usually run by your ISP or a public service such as Cloudflare's 1.1.1.1 or Google's 8.8.8.8. The resolver does the legwork.
If the resolver has no saved answer, it starts at a root server. The root server doesn't know the address, but it knows who runs .com, so it refers the resolver to a TLD server (TLD stands for top-level domain). The .com server refers it on to the domain's authoritative name server, the one that holds the domain's records. That server returns the IP address, and the resolver passes it back to your browser.
Here is the whole lookup for example.com, from browser to name server:
A DNS lookup for example.com, from browser to name server
Step 1 of 9: You type example.com, and the browser asks the resolver for its address.
Wondering how this was made? How we make these