DNS

Slow DNS on a Mac

Every new site needs a DNS lookup before it can load. A slow resolver adds a delay to the start of each page, even on a fast connection.

Applies to: macOS 13 Ventura and later for the System Settings steps. The Terminal commands work on all current macOS versions.Checked: 29 October 2026

Symptoms

  • A page waits for some seconds, then loads quickly.
  • The first visit to a site is slow, and the second visit is fast.
  • Speed tests show a good result, but browsing feels slow.

Likely causes

  • A slow or busy DNS server. The router or the provider's DNS server answers slowly.
  • A DNS server that does not answer. If the first server times out, the resolver tries the next one. Each timeout adds a delay.
  • Too many search domains. For a short name, the resolver tries each search domain in turn. Servers that are far away make this slow.
  • A VPN or filter in the path. A VPN can send all DNS queries through the tunnel to a server that is far away.

How to check

  1. Show the DNS servers and search domains that macOS uses.

    scutil --dns
  2. Measure one lookup through the macOS resolver. Do it two times. The second result can come from the cache.

    time dscacheutil -q host -a name example.org
  3. Look for search domains that you do not need.

    networksetup -getsearchdomains Wi-Fi

How to fix it

  1. Remove DNS servers that do not answer. Choose Apple menu > System Settings > Network.

  2. Click the network service, click Details, then click DNS. Remove the servers that do not answer.

  3. To use other DNS servers, click the Add button below the DNS Servers list and type the IP address.

  4. Remove search domains that you do not need. Use the Remove button below the Search Domains list.

  5. Restart the router if its DNS is slow for all devices.

  6. If nothing improves, remove your changes. An empty DNS Servers list uses the servers from the network again.

With Kilobat

  1. Compare the system resolver with Cloudflare, Google and Quad9. Run it two times before you decide.

    kilobat dns-benchmark

    Output One entry per resolver with resolver, milliseconds and replies out of 3.

  2. Split one slow site into DNS, connect, TLS and first byte.

    kilobat http-check https://example.org --json
  3. Change DNS from the CLI. macOS asks for an administrator password. Use automatic to go back.

    kilobat dns cloudflare
  4. The CLI is free. In the app, DNS switching is part of Pro, and Automatic stays free. See Pick a faster DNS.

Questions

Is a public DNS server always faster?

No. A resolver near you can be faster. Measure the system resolver and the public ones before you change.

Does flushing the DNS cache make DNS faster?

No. A flush removes old answers. The next lookups must go to the server again.

Sources

Sources checked on 29 October 2026. Man pages are the ones installed with macOS; open one with man <name> in Terminal.