> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/d/dns-domain-name-system.md).

# DNS (Domain Name System)

The phonebook of the Internet. Humans access information online through domain names, like nytimes.com or espn.com.

Web browsers interact through Internet Protocol (IP) addresses. DNS translates domain names to IP addresses so browsers can load Internet resources.

The Domain Name System (DNS) is a hierarchical, decentralized naming system that maps human-readable domain names (like example.com) to the numeric IP addresses (like 93.184.216.34) that computers use to identify each other on the network. DNS resolution involves a chain of queries through root servers, top-level domain servers, and authoritative name servers.

DNS record types serve different purposes. A records map domains to IPv4 addresses, AAAA records map to IPv6, CNAME records create aliases, and MX records direct email. TXT records store arbitrary text and are commonly used for domain verification and SPF/DKIM email authentication.

In API and serverless architectures, DNS is the entry point for all traffic. Custom domains for API endpoints require proper DNS configuration, often using CNAME records pointing to a gateway or CDN. DNS-based load balancing and geographic routing can direct API requests to the nearest edge location, reducing latency.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.serverlessapigateway.com/glossary/d/dns-domain-name-system.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.