---
title: What Is a DNS Server? How DNS Resolution Works
description: Learn what is a DNS server, how DNS resolution works, and how DNS resolvers and public DNS servers connect domains to IP addresses.
image: https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-20-2026-03-08-19-0480-PM.jpeg
---

[![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us)

[📘 Learn ▾](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us)

[CDN Fundamentals](https://blog.blazingcdn.com/cdn-fundamentals?hsLang=en-us) [By Content Type](https://blog.blazingcdn.com/by-content-type?hsLang=en-us) [Advanced Concepts](https://blog.blazingcdn.com/advanced-concepts?hsLang=en-us) [📖 Glossary](https://blog.blazingcdn.com/glossary?hsLang=en-us)

[🎬 Video & Streaming ▾](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us)

[🔴 Live Streaming](https://blog.blazingcdn.com/live-streaming?hsLang=en-us) [📺 VOD & OTT](https://blog.blazingcdn.com/vod-ott?hsLang=en-us) [🎞️ Encoding & Players](https://blog.blazingcdn.com/encoding-players?hsLang=en-us) [🎧 Audio & Podcasts](https://blog.blazingcdn.com/audio-podcasts?hsLang=en-us) [💰 Bandwidth & Costs](https://blog.blazingcdn.com/bandwidth-costs?hsLang=en-us)

[🏗️ Infrastructure ▾](https://blog.blazingcdn.com/cdn-infrastructure?hsLang=en-us)

[🗄️ Storage & Origin](https://blog.blazingcdn.com/storage-origin?hsLang=en-us) [📦 Large File Delivery](https://blog.blazingcdn.com/large-file-delivery?hsLang=en-us) [💸 Cloud Costs & Egress](https://blog.blazingcdn.com/cloud-costs-egress?hsLang=en-us) [🌐 Networking & ISP](https://blog.blazingcdn.com/networking-isp?hsLang=en-us) [⚙️ DevOps & Cloud Infra](https://blog.blazingcdn.com/devops-cloud-infra?hsLang=en-us) [⚡ Web Performance](https://blog.blazingcdn.com/web-performance?hsLang=en-us)

[🏭 Industries ▾](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us)

[📺 Media & Broadcasting](https://blog.blazingcdn.com/media-broadcasting?hsLang=en-us) [💾 Software & SaaS](https://blog.blazingcdn.com/software-saas?hsLang=en-us) [📣 AdTech & Advertising](https://blog.blazingcdn.com/adtech-advertising?hsLang=en-us) [🎮 Gaming & Esports](https://blog.blazingcdn.com/gaming-esports?hsLang=en-us) [📱 Mobile Apps & Developers](https://blog.blazingcdn.com/mobile-apps-developers?hsLang=en-us) [🤖 AI & Machine Learning](https://blog.blazingcdn.com/ai-machine-learning?hsLang=en-us) [🏛️ Enterprise & Corporate](https://blog.blazingcdn.com/enterprise-corporate?hsLang=en-us) [📚 E-Learning & EdTech](https://blog.blazingcdn.com/e-learning-edtech?hsLang=en-us) [🏟️ Sports & Live Events](https://blog.blazingcdn.com/sports-live-events?hsLang=en-us)

[💰 Pricing & Compare ▾](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us)

[Provider Pricing](https://blog.blazingcdn.com/provider-pricing?hsLang=en-us) [Cost Optimization](https://blog.blazingcdn.com/cost-optimization?hsLang=en-us) [Decision Support](https://blog.blazingcdn.com/decision-support?hsLang=en-us) [⚡ Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [Provider Comparisons](https://blog.blazingcdn.com/provider-comparisons?hsLang=en-us) [Strategy Comparisons](https://blog.blazingcdn.com/strategy-comparisons?hsLang=en-us) [📊 Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us)

[🔒 Security ▾](https://blog.blazingcdn.com/cdn-security?hsLang=en-us)

[Attack Protection](https://blog.blazingcdn.com/attack-protection?hsLang=en-us) [Encryption & Access](https://blog.blazingcdn.com/encryption-access?hsLang=en-us) [Video & DRM Security](https://blog.blazingcdn.com/video-drm-security?hsLang=en-us)

[🛠️ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us)

[Get Started](https://blazingcdn.com/sign-up-contact-form/)

[Infrastructure](https://blog.blazingcdn.com/en-us/tag/infrastructure) [Infrastructure - Networking & ISP](https://blog.blazingcdn.com/en-us/tag/infrastructure-networking-isp)

# What Is a DNS Server? How DNS Resolution Works

 Vadym Borovskyi  Nov 20, 2026, 4:10:08 PM

![\<span id="hs\_cos\_wrapper\_name" class="hs\_cos\_wrapper hs\_cos\_wrapper\_meta\_field hs\_cos\_wrapper\_type\_text" style="" data-hs-cos-general-type="meta\_field" data-hs-cos-type="text" \>What Is a DNS Server? How DNS Resolution Works\</span\>](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-20-2026-03-08-19-0480-PM.jpeg)

A **DNS server** is a networked service that answers Domain Name System queries, translating a hostname such as www.example.com into records like an IPv4 address (A), an IPv6 address (AAAA) or an alias (CNAME). It listens on UDP and TCP port 53, and one uncached lookup usually touches four server roles: recursive resolver, root, top-level domain (TLD) and authoritative.

As of 2026, the DNS root is served by 13 lettered root server identities, A through M, operated by 12 independent organizations and replicated through anycast at well over 1,000 sites worldwide. Because resolvers cache every answer for its time to live (TTL), most lookups never reach the root: a warm resolver cache answers in well under a millisecond of server time, while a cold lookup typically costs 50 to 200 ms (estimate).

## **How a DNS server resolves a name, step by step**

A full resolution is a chain of referrals. The recursive resolver does the walking; every other server only answers for the zone it is responsible for. For a cold lookup of www.example.com:

1. The stub resolver in the operating system checks its local cache and the hosts file, then sends a query with the Recursion Desired (RD) flag to its configured resolver.
2. The recursive resolver checks its cache. On a hit it answers immediately, and the lookup ends here for most queries.
3. On a miss it asks a root server, chosen from its built-in root hints. The root returns a referral: the NS records for the .com TLD plus glue (their A and AAAA records). With QNAME minimisation (RFC 9156) the resolver sends only "com", not the full name.
4. It asks a .com TLD server, which returns a referral to the authoritative nameservers for example.com, with glue when those nameservers sit inside the zone.
5. The authoritative server returns the answer with the Authoritative Answer (AA) flag set. If the answer is a CNAME, the resolver restarts the chase for the target name; CDN hostnames commonly add one or two such hops.
6. If DNSSEC validation is on, the resolver checks RRSIG signatures against the DS chain from the root down, then caches each record for its TTL and returns the result to the stub.

The referral data is the reason steps 3 and 4 are rare. TLD delegations in the root zone carry a 172,800-second TTL (two days), so a busy resolver almost never asks the root about .com.

## **The four types of DNS server**

### Recursive DNS resolver

A DNS resolver (recursive resolver) accepts queries from clients, performs the referral walk on their behalf and caches results. It is the only role that holds state on behalf of users: positive answers, negative answers (cached from the SOA record per RFC 2308) and delegations. Unbound, BIND, Knot Resolver and PowerDNS Recursor are common implementations.

### Root server

Root servers are authoritative for the root zone only. They never resolve names; they hand out referrals to TLD nameservers.

### TLD server

TLD servers are authoritative for zones such as .com, .org or .de, and return referrals to the nameservers each registered domain has delegated to.

### Authoritative nameserver

The authoritative server holds the actual zone data and is where operators set records and TTLs. Managed DNS providers and CDN request-routing systems run at this layer, often computing answers per query rather than reading a static zone.

## **Why DNS speed matters, with the cache math**

DNS time is paid before the TCP and TLS handshakes, so it adds directly to time to first byte on every new hostname. Whether a user pays it depends almost entirely on the resolver cache hit ratio, and that ratio is a function of query rate and TTL. With steady traffic, a resolver cache fetches upstream roughly once per TTL window, so the miss ratio is about one divided by (queries per second times TTL in seconds), capped at 100%.

| Queries reaching one resolver cache | Miss ratio at TTL 30 s | Miss ratio at TTL 300 s |
| --- | --- | --- |
| 100 per second | 1 in 3,000 (0.03%) | 1 in 30,000 (0.003%) |
| 1 per second | 1 in 30 (3.3%) | 1 in 300 (0.33%) |
| 1 per minute | Every query (100%) | 1 in 5 (20%) |

Short TTLs are nearly free for popular hostnames and expensive for long-tail ones, because a low-traffic name on a 30-second TTL misses on every lookup.

At a 150 ms cold cost, the 1-per-minute row adds an average of 150 ms per lookup at TTL 30 and 30 ms at TTL 300. The trap at scale is cache fragmentation: large public resolvers spread one IP address across many anycast sites, each with separate caches, so a hostname that looks popular globally can behave like the bottom row at each individual cache.

## **Where the DNS server sits in a CDN request path**

Most CDNs steer users at the authoritative layer: your hostname is a CNAME to the provider, whose nameservers return an edge address chosen per resolver, or per client subnet when the resolver sends EDNS Client Subnet (RFC 7871). Anycast CDNs return a stable address and let BGP pick the site, which makes the answer cacheable for longer. The same layer is how teams add a second provider: BlazingCDN can run as a second CDN behind DNS with a weighted traffic split, using Anycast routing with built-in failover, as described on its [**multi-CDN integration behind weighted DNS**](https://blazingcdn.com/multi-cdn-integration/) page.

## **DNS server vs. its commonly confused neighbors**

**Recursive resolver vs. authoritative server:** the resolver asks questions and caches answers for clients; the authoritative server owns the zone and only answers for it. Mixing both roles on one host is discouraged because it exposes the authoritative service to cache poisoning and amplification abuse.

**DNS resolver vs. stub resolver:** the stub is the client library in the operating system or browser that sends a single recursive query and trusts the reply. It performs no referral walk, although browsers and systemd-resolved keep short local caches.

**Public DNS servers vs. ISP resolvers:** public DNS servers such as Cloudflare 1.1.1.1, Google Public DNS 8.8.8.8 and Quad9 9.9.9.9 are anycast recursive resolvers open to anyone. They are often closer and better maintained than ISP resolvers, but Cloudflare's resolver does not send EDNS Client Subnet, so a CDN maps those users by resolver location rather than client location.

## **A realistic resolver configuration, in words**

On an Unbound recursive resolver, set **prefetch** to yes so popular records are refreshed when they enter the last 10% of their TTL, removing most cold misses for busy names. Set **serve-expired** to yes to answer from stale data while refreshing (the serve-stale behavior of RFC 8767), which keeps resolution working when an authoritative server is briefly unreachable. Leave **qname-minimisation** on, size **rrset-cache-size** at roughly twice **msg-cache-size**, and leave **cache-min-ttl** at zero, because raising it overrides operators who deliberately use short TTLs for failover.

## **Common misconceptions about DNS servers**

- **"DNS propagation" is not a push.** Nothing propagates; resolvers keep old answers until the TTL they cached expires.
- **Lowering a TTL just before a migration does not help.** Resolvers holding the old 86,400-second record keep it for up to a day, so drop the TTL at least one old TTL ahead.
- **DNS is not UDP-only.** TCP support is mandatory (RFC 7766), and DNS Flag Day 2020 recommended a 1,232-byte EDNS buffer, so large DNSSEC answers truncate and retry over TCP.
- **Encrypted DNS changes transport, not resolution.** DNS over TLS (RFC 7858, port 853) and DNS over HTTPS (RFC 8484) protect the stub-to-resolver hop only.

## **FAQ: DNS server basics engineers search for**

### What is the difference between a DNS server and a DNS resolver?

A DNS resolver is one type of DNS server: the recursive kind that walks referrals and caches answers for clients. "DNS server" also covers root, TLD and authoritative nameservers, which only answer for their own zones. When an operating system asks for a "DNS server" address, it means the recursive resolver it should send queries to.

### Are public DNS servers faster than my ISP's DNS server?

Public DNS servers are often faster, but not universally. Anycast resolvers like 1.1.1.1 and 8.8.8.8 are usually close and well cached, yet an ISP resolver inside your access network can answer in a few milliseconds. Resolvers that omit EDNS Client Subnet can also make CDNs choose a more distant edge, so measure both paths.

### How long does a DNS server cache a record?

A recursive DNS server caches a record for the TTL set by the authoritative zone, counting down from when it received the answer. Resolvers also apply caps: Unbound limits cached TTLs to one day by default, and negative answers are cached for the SOA minimum or SOA TTL, whichever is lower, per RFC 2308.

### Which port does a DNS server use?

A standard DNS server listens on port 53 over both UDP and TCP. UDP carries most queries, while TCP handles truncated large responses and zone transfers. Encrypted variants use other ports: DNS over TLS runs on port 853, and DNS over HTTPS uses port 443, which makes it indistinguishable from ordinary web traffic on the network.

## **Measure your own DNS resolution time this week**

Run dig against your production hostnames from three vantage points: your default resolver, 1.1.1.1 and 8.8.8.8. Record the query time line on a first and second run to separate cold from warm cost, then use the trace option to see every referral hop and the TTL on each CNAME in your CDN chain. In real user monitoring, chart the gap between domainLookupStart and domainLookupEnd in the Resource Timing API by country; any hostname where p75 exceeds 50 ms is a candidate for a longer TTL or fewer CNAME hops. If the CNAME you are tuning points at a CDN, the [**BlazingCDN Anycast CDN**](https://blazingcdn.com/anycast-cdn/) page explains its Anycast routing with built-in failover, which returns a stable address a resolver can cache.

Share: [f](https://www.facebook.com/sharer/sharer.php?u=https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works) [in](https://www.linkedin.com/sharing/share-offsite/?url=https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works) [𝕏](https://twitter.com/intent/tweet?url=https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works&text=) [✉](mailto:?subject=%3Cspan%20id="hs_cos_wrapper_name"%20class="hs_cos_wrapper%20hs_cos_wrapper_meta_field%20hs_cos_wrapper_type_text"%20style=""%20data-hs-cos-general-type="meta_field"%20data-hs-cos-type="text"%20%3EWhat%20Is%20a%20DNS%20Server?%20How%20DNS%20Resolution%20Works%3C/span%3E&body=https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works)

![BlazingCDN](https://blog.blazingcdn.com/hs-fs/hubfs/Logo/blog-logo-w.png?height=24&name=blog-logo-w.png)

*Heavy traffic.*  
Light bill.

The CDN for video and large traffic

100 TB a month at list price

- BlazingCDN**$415**
- [bunny.net](https://bunny.net/pricing/) Volume**$500**
- [CDN77](https://www.cdn77.com/pricing), plan to 250 TB**$990**
- [KeyCDN](https://www.keycdn.com/pricing), NA and Europe**$2,600**
- [CloudFront](https://aws.amazon.com/cloudfront/pricing/pay-as-you-go/) pay as you go**$6,965**

Each provider's published list price for transfer, lowest first, checked November 2026. BlazingCDN publishes this blog. Up to 50 TB a month a flat plan such as CloudFront Pro ($15) can cost less.

[Calculate your cost](https://blazingcdn.com/cdn-cost-calculator/?utm_source=blog&utm_medium=sidebar&utm_campaign=blog_sidebar&utm_content=compare_calc)

## Related posts

[![What Is IPv6? IPv6 vs IPv4 and Why It Matters](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-07-50-38-8948-AM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-ipv6-ipv6-vs-ipv4-and-why-it-matters?hsLang=en-us)

Infrastructure

### [What Is IPv6? IPv6 vs IPv4 and Why It Matters](https://blog.blazingcdn.com/en-us/what-is-ipv6-ipv6-vs-ipv4-and-why-it-matters?hsLang=en-us)

The short answer to what is IPv6: Internet Protocol version 6 is the network-layer protocol that replaces IPv4's 32-bit ...

Nov 4, 2026, 8:52:25 AM [Read more](https://blog.blazingcdn.com/en-us/what-is-ipv6-ipv6-vs-ipv4-and-why-it-matters?hsLang=en-us)

[![What Is a Network Port? Ports 80 and 443 Explained](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-05-45-38-9119-AM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-a-network-port-ports-80-and-443-explained?hsLang=en-us)

Infrastructure

### [What Is a Network Port? Ports 80 and 443 Explained](https://blog.blazingcdn.com/en-us/what-is-a-network-port-ports-80-and-443-explained?hsLang=en-us)

The short answer to what is a port: a network port is a 16-bit number, from 0 to 65535, carried in every TCP and UDP ...

Nov 4, 2026, 6:47:39 AM [Read more](https://blog.blazingcdn.com/en-us/what-is-a-network-port-ports-80-and-443-explained?hsLang=en-us)

[![DNS Propagation: Why DNS Changes Take Time](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-03-40-38-3827-AM.jpeg)](https://blog.blazingcdn.com/en-us/dns-propagation-why-dns-changes-take-time?hsLang=en-us)

Infrastructure

### [DNS Propagation: Why DNS Changes Take Time](https://blog.blazingcdn.com/en-us/dns-propagation-why-dns-changes-take-time?hsLang=en-us)

DNS propagation is the window after a record change during which recursive resolvers, operating system caches and ...

Nov 4, 2026, 4:42:52 AM [Read more](https://blog.blazingcdn.com/en-us/dns-propagation-why-dns-changes-take-time?hsLang=en-us)

[![DNS Records Explained: A, AAAA, CNAME, TXT and More](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-01-35-38-5774-AM.jpeg)](https://blog.blazingcdn.com/en-us/dns-records-explained-a-aaaa-cname-txt-and-more?hsLang=en-us)

Infrastructure

### [DNS Records Explained: A, AAAA, CNAME, TXT and More](https://blog.blazingcdn.com/en-us/dns-records-explained-a-aaaa-cname-txt-and-more?hsLang=en-us)

DNS records are typed entries in an authoritative zone that map a name to data. An A record returns a 32-bit IPv4 ...

Nov 4, 2026, 2:37:32 AM [Read more](https://blog.blazingcdn.com/en-us/dns-records-explained-a-aaaa-cname-txt-and-more?hsLang=en-us)

[![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us)

[📘 Learn](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us) [📊 Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [🎬 Video & Streaming](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us) [🏭 Industries](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us) [💰 Pricing & Costs](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us) [⚡ Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [🔒 Security](https://blog.blazingcdn.com/cdn-security?hsLang=en-us) [🛠️ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us) [✍️ Publish with us](https://blog.blazingcdn.com/publish-with-us?hsLang=en-us)

in f 𝕏 ✉

 Copyright © BlazingCDN |. All rights reserved.

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blazingcdn.com/#organization",
  "@type" : "Organization",
  "description" : "High-volume CDN for video, live streaming, OTT/IPTV, software, games, SaaS and large-file delivery.",
  "logo" : {
    "@id" : "https://blazingcdn.com/#logo",
    "@type" : "ImageObject",
    "height" : 560,
    "url" : "https://blazingcdn.com/wp-content/uploads/2024/08/logo-560-560.png",
    "width" : 560
  },
  "name" : "BlazingCDN",
  "sameAs" : [ "https://www.linkedin.com/company/blazingcdn", "https://x.com/BlazingCdn", "https://www.reddit.com/r/BlazingCDN/", "https://www.wikidata.org/wiki/Q141711074" ],
  "url" : "https://blazingcdn.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/#website",
  "@type" : "WebSite",
  "inLanguage" : "en-US",
  "name" : "BlazingCDN Blog",
  "publisher" : {
    "@id" : "https://blazingcdn.com/#organization"
  },
  "url" : "https://blog.blazingcdn.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works#article",
  "@type" : "BlogPosting",
  "author" : {
    "@id" : "https://blog.blazingcdn.com/en-us/author/blazingcdn#person",
    "@type" : "Person",
    "description" : "Vadym Borovskyi is Chief Product and Marketing Officer at BlazingCDN, where he has led product strategy and growth since 2021. He has more than 11 years of experience in IT product management and B2B marketing. On this blog he writes about CDN pricing and egress costs, video and software delivery, cache configuration, and how teams evaluate and switch CDN providers. He is based in Warsaw, Poland.",
    "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/vadym-borovskyi.jpg",
    "jobTitle" : "Chief Product and Marketing Officer",
    "knowsAbout" : [ "Content Delivery Networks (CDN)", "CDN pricing", "Video streaming delivery", "Software and game distribution", "Cache optimization", "Product Management", "B2B Marketing", "Digital Marketing", "Pay Per Click Marketing (PPC)", "Google Ads", "Search Engine Marketing (SEM)", "Marketing Strategy", "Artificial Intelligence (AI)", "Cloud Management", "SaaS Development", "IT Consulting", "Computer Networking", "Project Management", "Startups" ],
    "name" : "Vadym Borovskyi",
    "sameAs" : [ "https://www.linkedin.com/in/axelt/" ],
    "url" : "https://blog.blazingcdn.com/en-us/author/blazingcdn",
    "worksFor" : {
      "@id" : "https://blazingcdn.com/#organization"
    }
  },
  "dateModified" : "2026-11-20T15:10:08Z",
  "datePublished" : "2026-11-20T15:10:08Z",
  "description" : "Learn what is a DNS server, how DNS resolution works, and how DNS resolvers and public DNS servers connect domains to IP addresses.",
  "headline" : "What Is a DNS Server? How DNS Resolution Works",
  "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/Gemini-Blog/image-Nov-20-2026-03-08-19-0480-PM.jpeg",
  "inLanguage" : "en-us",
  "isPartOf" : {
    "@id" : "https://blog.blazingcdn.com/#website"
  },
  "mainEntityOfPage" : {
    "@id" : "https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@id" : "https://blazingcdn.com/#organization"
  },
  "wordCount" : 1693
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works#breadcrumb",
  "@type" : "BreadcrumbList",
  "itemListElement" : [ {
    "@type" : "ListItem",
    "item" : "https://blog.blazingcdn.com/en-us",
    "name" : "Blog",
    "position" : 1
  }, {
    "@type" : "ListItem",
    "item" : "https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works",
    "name" : "What Is a DNS Server? How DNS Resolution Works",
    "position" : 2
  } ]
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/what-is-a-dns-server-how-dns-resolution-works#faq",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "A DNS resolver is one type of DNS server: the recursive kind that walks referrals and caches answers for clients. \"DNS server\" also covers root, TLD and authoritative nameservers, which only answer for their own zones. When an operating system asks for a \"DNS server\" address, it means the recursive resolver it should send queries to."
    },
    "name" : "What is the difference between a DNS server and a DNS resolver?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Public DNS servers are often faster, but not universally. Anycast resolvers like 1.1.1.1 and 8.8.8.8 are usually close and well cached, yet an ISP resolver inside your access network can answer in a few milliseconds. Resolvers that omit EDNS Client Subnet can also make CDNs choose a more distant edge, so measure both paths."
    },
    "name" : "Are public DNS servers faster than my ISP's DNS server?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "A recursive DNS server caches a record for the TTL set by the authoritative zone, counting down from when it received the answer. Resolvers also apply caps: Unbound limits cached TTLs to one day by default, and negative answers are cached for the SOA minimum or SOA TTL, whichever is lower, per RFC 2308."
    },
    "name" : "How long does a DNS server cache a record?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "A standard DNS server listens on port 53 over both UDP and TCP. UDP carries most queries, while TCP handles truncated large responses and zone transfers. Encrypted variants use other ports: DNS over TLS runs on port 853, and DNS over HTTPS uses port 443, which makes it indistinguishable from ordinary web traffic on the network."
    },
    "name" : "Which port does a DNS server use?"
  } ]
}
```