---
title: "Fastest DNS server for Mac: test it on your own connection with dig · Kilobat Guides"
url: "https://kilobat.app/guides/fastest-dns-server-mac"
description: "The fastest DNS server depends on your network. Measure it on your Mac with dig, or let Kilobat's Fastest DNS time the choices on each network."
---

# Fastest DNS server for a Mac: how to measure it

The fastest DNS server is the one that answers fastest from your network. That differs by place, provider and hour. Measure it with `dig`, or let Kilobat time the choices on each network.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

My Mac has this problem: Fastest DNS server for a Mac: how to measure it. Read https://kilobat.app/guides/fastest-dns-server-mac.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Applies to: All current macOS versions. `dig` is installed with macOS. · Checked: 8 November 2026

## When this helps

- You read that one public DNS is the fastest and want to check it on your own connection.
- Pages pause before they start to load.
- You moved to a new network and want the best DNS there.

## Why no list can name one

A DNS resolver answers fast when a server is near you and the answer is in its cache. Both change with your network and the time of day.

A test on another connection says little about yours. Test on the network where you use the Mac.

A fast lookup is also not the whole result. A resolver can hand back a web server that is far from you. The page then connects slower, even though the lookup was fast.

## Measure it free with dig

1. Open Terminal. Ask your network's DNS for a site and read the query time.

   ```
   dig apple.com | grep "Query time"
   ```
2. Ask Cloudflare the same question.

   ```
   dig @1.1.1.1 apple.com | grep "Query time"
   ```
3. Do the same for Google and Quad9. Use 8.8.8.8 and 9.9.9.9.

   ```
   dig @8.8.8.8 apple.com | grep "Query time"
   ```
4. Run each one several times, with several sites. The first lookup is slower than a repeat, because the cache is cold.
5. To test many at once, loop over the servers and sites.

   ```
   for s in 1.1.1.1 8.8.8.8 9.9.9.9; do for n in apple.com wikipedia.org; do echo -n "$s $n "; dig @$s $n +tries=1 +time=2 | awk '/Query time/{print $4" ms"}'; done; done
   ```
6. Compare the times. Ignore a difference of a few ms. Also look for failures, which show no query time.

A few runs give a rough guide. For a fair comparison, repeat it at different times of day. Then read [Best DNS server for a Mac: Cloudflare, Google, Quad9 and others](https://kilobat.app/guides/best-dns-server-mac) before you choose, because filtering and logging differ.

## Let Kilobat time it on each network

Kilobat's Fastest DNS runs the comparison for you, on the network you are on. It lives in the app under Health › DNS.

- **What it times.** Your network's own DNS against Cloudflare, Quad9 and Google, and any resolver you add. It uses about two dozen lookups each.
- **What it measures.** The first lookup of popular sites, a repeat of the same names, and how fast the web servers in the answers connect. A resolver that returns far servers is marked.
- **What it flags.** A resolver whose lookups fail, and a network DNS that answers names that do not exist, usually to show ads or a search page.
- **When it runs.** Quietly, a few times a day. It does not run on metered networks, through a VPN or behind a sign-in page.
- **How it decides.** Kilobat can switch to the fastest on joining a network, after one has won there on 3 days. It goes back to the network's DNS for a VPN, a sign-in page or failing lookups.

To run it now, click Test now in Health › DNS. The result is a table of the resolvers, with the median time for each. See [Pick a faster DNS](https://kilobat.app/guides/recipes/pick-faster-dns).

## With Kilobat

1. Show the result for this network. Add `--all` for every network.

   ```
   kilobat dns fastest
   ```
2. Time the system resolver against Cloudflare, Google and Quad9 once.

   ```
   kilobat dns-benchmark
   ```
3. Never time or pick a resolver. Use `include` to undo it.

   ```
   kilobat dns exclude google
   ```
4. Set a resolver to use when the fastest fails.

   ```
   kilobat dns fallback cloudflare
   ```

## Questions

**Is 1.1.1.1 the fastest DNS?**

It can be, on some networks. On others a different resolver or your provider's DNS wins. Measure on yours.

**Why does the same lookup take less time the second time?**

The resolver keeps the answer in its cache. A repeat tests the round trip. The first lookup includes the work of finding the answer.

**Does a faster DNS raise my download speed?**

No. It shortens the pause before a connection starts. See [Slow DNS on a Mac](https://kilobat.app/guides/slow-dns-mac).

**Does fast DNS lower my ping in games?**

No. See [Best DNS for gaming: what it changes and what it does not](https://kilobat.app/guides/best-dns-for-gaming).

## Sources

- dig(1), man page installed with macOS

Checked on 8 November 2026.

## Related guides

- [Best DNS server for a Mac: Cloudflare, Google, Quad9 and others](https://kilobat.app/guides/best-dns-server-mac): No DNS server is best for everyone.
- [Pick a faster DNS](https://kilobat.app/guides/recipes/pick-faster-dns): Slow DNS makes every new site slow to start.
- [Slow DNS on a Mac](https://kilobat.app/guides/slow-dns-mac): Every new site needs a DNS lookup before it can load.
- [Best DNS for gaming: what it changes and what it does not](https://kilobat.app/guides/best-dns-for-gaming): Changing your DNS server does not lower your in-game ping.
