> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/dns/what-is-dns.md).

# What is DNS?

The **DNS (Domain Name System )** is a core internet protocol that translates human-readable domain names into numerical IP addresses required for network communication.\
It acts as a distributed, hierarchical database that allows browsers, applications, and APIs to locate online resources efficiently.\
Within **Medianova’s infrastructure**, DNS provides the critical mapping layer that directs user requests to the correct CDN Resource or Redirect endpoint, ensuring consistent performance and service availability.

#### **How DNS Works**

DNS operates through a global hierarchy of **root**, **top-level domain (TLD)**, and **authoritative name servers**, each responsible for part of the name resolution process.\
When a query is initiated, recursive resolvers traverse this hierarchy, cache responses, and return the authoritative record for the requested domain.

```plaintext
Root (.)
 └── TLDs (com, org, net, tr)
      └── Domains (example.com)
           └── Subdomains (cdn.example.com)
```

Each DNS record type serves a specific purpose:

* **A / AAAA:** Map domain names to IPv4 or IPv6 addresses.
* **CNAME:** Alias one domain to another, often used to connect a branded hostname (e.g., `cdn.yourdomain.com`) to a Medianova CDN Resource (`yourzonename.mncdn.com`).
* **MX / TXT / SRV:** Support email routing, domain verification, and service discovery.

For additional details on configuring CNAME records within Medianova, see [CNAME & SSL](/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md).

#### **DNS in the Medianova**

DNS is not just a prerequisite for routing traffic — it is an integrated layer of Medianova’s delivery architecture.

**Within Medianova services, DNS enables:**

* **Zone-based configuration:** Each CDN Resource or Redirect domain operates within a defined DNS Zone.
* **Anycast routing:** Queries are automatically resolved through the closest available authoritative node for improved reliability and reduced lookup latency.
* **Secure HTTPS mapping:** Combined with SSL/TLS certificates to ensure encrypted access.
* **Redirect operations:** Medianova’s Redirect feature uses DNS mapping for efficient domain-level forwarding.

By integrating these mechanisms, Medianova ensures optimized name resolution, minimized propagation delays, and high query availability across its global network.

#### **Technical Summary**

<table><thead><tr><th width="206">Component</th><th>Description</th></tr></thead><tbody><tr><td><strong>Protocol</strong></td><td>Primarily UDP (port 53) for queries, TCP for zone transfers and large payloads</td></tr><tr><td><strong>Caching</strong></td><td>Reduces recursive lookup time and query load</td></tr><tr><td><strong>Record Types</strong></td><td>A, AAAA, CNAME, MX, TXT, SRV, PTR</td></tr><tr><td><strong>Security Extensions</strong></td><td>DNSSEC, CAA, TLSA support</td></tr><tr><td><strong>Integration</strong></td><td>Used by Medianova CDN, Redirect, and CNAME &#x26; SSL configurations</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/products/dns/what-is-dns.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.