Editing DNS Resolution (section)

== DNS Lookup Flow ==

The process of DNS resolution involves multiple steps from your device to authoritative servers. The system is designed hierarchically and follows a strict delegation of responsibility.

=== Local DNS Cache ===

The resolver on the client machine first checks its local cache:
- If the domain is found in memory and has not expired (TTL), the IP address is returned immediately.
- If not, it proceeds to ask a configured recursive resolver.

=== Recursive Resolver ===

A recursive resolver (often provided by an ISP or manually configured) attempts to resolve the domain by checking:
- Its own cache
- If not cached, it performs a full DNS traversal starting from the root

=== Root Servers ===

Root servers do not contain specific domain records. They direct the resolver to the correct Top-Level Domain (TLD) servers, based on domain suffix (e.g., `.com`, `.org`, `.net`, `.no`).

Example:


=== TLD Servers ===

TLD servers maintain information about which authoritative name servers are responsible for domains under that TLD. For `.com`, the TLD server points to the name server managing `example.com`.

=== Authoritative Name Server ===

The authoritative server holds the definitive DNS records for the domain. This is the final step in the lookup process and returns the relevant DNS record type (A, MX, etc.).