> 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/common-dns-misconceptions.md). # Common DNS Misconceptions Learn about common misunderstandings in DNS configuration and how Medianova DNS addresses them for consistent performance and reliability. DNS is one of the most widely deployed yet frequently misunderstood internet systems.\ Even small configuration errors can lead to propagation delays, traffic misdirection, or downtime.\ This page explains common misconceptions about DNS behavior and clarifies how **Medianova DNS** manages these factors through optimized TTL policies, Anycast resolution, and real-time zone updates. ### **“DNS Is Instantaneous”** **Misconception:**\ Changes to DNS records are instantly visible across the internet. **Reality:**\ DNS lookups may appear instant due to caching, but propagation is constrained by several factors: * TTL (Time to Live) values assigned to each record * Intermediate caches in browsers, operating systems, and recursive resolvers * Update intervals for authoritative nameservers Even with low TTL settings, caches that already exist cannot be invalidated immediately.\ **Medianova DNS** minimizes propagation latency through fast Anycast-based resolvers and controlled TTL management per record. Related: [How DNS Works – Step by Step](/products/dns/how-dns-works-step-by-step.md) ### **“Changing DNS Records Moves Traffic Instantly”** **Misconception:**\ Updating a DNS record instantly redirects all active traffic. **Reality:**\ DNS does not behave like a real-time routing protocol (e.g., BGP).\ Record updates only affect **new DNS lookups**, not ongoing sessions using cached data.\ Existing clients will continue to use the previous IP or CNAME value until their TTL expires. To manage controlled transitions, **Medianova** recommends: * Lowering TTL in advance of planned migrations * Using temporary records to pre-warm caches * Coordinating updates with CDN Resource or Redirect configuration changes See [Redirect](/products/dns/redirect.md) and [CNAME & SSL](/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md). ### **“CNAMEs Can Be Used Anywhere”** **Misconception:**\ [CNAME](/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md) records can be freely applied to any domain name. **Reality:**\ CNAME cannot coexist with other record types (A, MX, TXT) for the same name.\ They are also **not allowed at the zone apex** (e.g., `example.com`) unless the DNS provider supports special record types like **ALIAS** or **ANAME**. In **Medianova DNS**, CNAMEs are primarily used to map customer domains (e.g., `cdn.yourdomain.com`) to Medianova CDN hostnames (`yourzonename.mncdn.com`).\ Zone apex mapping should be handled via redirects or A records. ### **“DNS Is Secure by Default”** **Misconception:**\ DNS queries are protected against interception or tampering. **Reality:**\ Traditional DNS operates in plaintext and offers no integrity or confidentiality.\ Without added security mechanisms, attackers can perform: * **DNS spoofing or cache poisoning** * **Record hijacking** * **Traffic interception through rogue resolvers** **Medianova DNS** supports security extensions such as **DNSSEC**, **CAA**, and **TLSA** to ensure query authenticity and HTTPS certificate validation. ### **“TTL Is Just a Performance Setting”** **Misconception:**\ TTL only affects caching speed and can be adjusted arbitrarily. **Reality:**\ TTL is a **critical operational parameter**.\ Improper TTL management can: * Extend the lifespan of outdated or incorrect records * Prevent quick rollbacks during outages * Delay failover routing updates In **Medianova DNS**, TTL is configurable per record, allowing flexible trade-offs between performance and control.\ Short TTLs are recommended for frequently updated records such as **Redirects** or **load-balancing CNAMEs**. --- # 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://clients.medianova.com/products/dns/common-dns-misconceptions.md?ask=&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.