Networks
The quiet work of DNS.
Before most connections begin, a name has to become an address. A short guide to that first step.
From a name to an address
People remember names more easily than numerical addresses. The Domain Name System, or DNS, helps turn a name into the information an application needs to connect. A resolver can return an answer it already has in its cache, or find an answer through other DNS servers.
This lookup is one stage in loading a page. After it succeeds, the application still needs a working connection to the destination. A DNS answer is not a guarantee that the service behind the address is available.
Why answers are cached
Caching avoids repeating the same work for every request. DNS records include a time-to-live value that helps determine how long an answer can be reused. Caches may exist at several points, including in an application, the operating system and a resolver.
This is why changing a DNS record may not be visible everywhere immediately. It is also why repeated tests do not always measure the same thing as a first visit.
Know what you are testing
When a page will not load, first check whether its name resolves. Then check whether the returned address is reachable and whether the service responds. Keeping those questions separate makes troubleshooting more efficient.
Changing a resolver can help with a resolver-specific problem. It will not repair a broken server or a disconnected network cable. Avoid changing several settings together, because a successful retry will then tell you very little about which change helped.
A small part of a larger journey
Encrypted DNS can protect the exchange between a client and a compatible resolver. It does not encrypt every other part of the connection, and the resolver still processes the query. Understanding the boundary of each tool makes it easier to use it appropriately.
Keep one known-working configuration and a short record of what changed. A reversible experiment is easier to learn from.