Przejdź do treści
Biblioteka skilli
DevOps i chmura · Analiza

mac-dns-troubleshooting

/mac-dns-troubleshooting

Diagnozuje DNS na Macu: mierzy czas odpowiedzi, porównuje resolvery Cloudflare, Google i Quad9 i zmienia ustawienia po zgodzie.

Repozytorium
kilobat-skills ↗
Licencja
GPL-3.0
Ostatnia zmiana repozytorium
07.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
5
Przestarzałość

Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

GPL-3.0, otwarta.

Co robi i kiedy

Diagnozuje DNS na Macu: mierzy czas odpowiedzi, porównuje resolvery Cloudflare, Google i Quad9 i zmienia ustawienia po zgodzie.

Wyzwalacze z opisu

server not found
Oryginalny opis (EN)

Diagnose and fix DNS on a Mac with Kilobat. Measures lookup time, benchmarks the system resolver against Cloudflare, Google and Quad9, switches DNS to Cloudflare, Google or Quad9 or flushes it with the user's approval, and builds an encrypted DNS (DNS-over-HTTPS) profile. Use when pages are slow to start, sites fail with "server not found", a hotel or café login page won't appear, or the user asks which DNS is fastest.

Jak działa

  1. Setup
  2. 1. Rule out a login page first
  3. 2. Measure the current resolver
  4. 3. Compare resolvers
  5. 4. Separate DNS from the site
  6. 5. Change DNS, with approval
  7. When the cause isn't clear: look up a guide
  8. 6. Verify
Sekcje z nagłówków SKILL.md, w oryginale · 64 linii, 1 211 słów
Podgląd SKILL.md
---
name: mac-dns-troubleshooting
description: Diagnose and fix DNS on a Mac with Kilobat. Measures lookup time, benchmarks the system resolver against Cloudflare, Google and Quad9, switches DNS to Cloudflare, Google or Quad9 or flushes it with the user's approval, and builds an encrypted DNS (DNS-over-HTTPS) profile. Use when pages are slow to start, sites fail with "server not found", a hotel or café login page won't appear, or the user asks which DNS is fastest.
---

# Mac DNS troubleshooting with Kilobat

DNS turns names into addresses before anything loads, so a slow or broken resolver makes every site feel slow to start even when the connection is fast. This skill measures DNS, compares resolvers and changes DNS only with the user's approval.

## Setup

Use the Kilobat MCP tools if connected, otherwise the `kilobat` CLI (`brew install seifip/kilobat/kilobat`, macOS 14+; ask before installing). Commands here need CLI 0.2 or later (`kilobat --version`); if one is unknown, suggest `brew upgrade kilobat`. Measuring is safe. Changing or flushing DNS shows a macOS administrator prompt and needs a clear yes first. The `kilobat` skill lists the rules.

## 1. Rule out a login page first

Run `kilobat diagnose --json`. If `measurements.captivePortal` is `true`, the network wants a login (hotel, café, plane, airport). `kilobat portal --json` gives the sign-in page and says whether the network logged them out after an earlier sign-in; `kilobat portal open` opens the page when they ask. Otherwise ask the user to open any http site in a browser to bring up the page. A custom DNS server can stop the page from appearing; if it never shows, offer `kilobat dns automatic` (with approval), log in, then switch back.

## 2. Measure the current resolver

From the same `diagnose` output:

- `measurements.dnsMilliseconds`: one lookup of example.com through the system resolver. Above 150 ms Kilobat rates DNS as degraded. Near 0 means a cached answer; run diagnose again or rely on the benchmark.
- `measurements.dnsServers`: the resolvers in use. Write them down before any change so they can be restored.
- `measurements.networkService`: the macOS service (for example `Wi-Fi`) that a DNS change applies to.

`kilobat dns` with no argument prints the current resolvers on their own.

## 3. Compare resolvers

If the Kilobat app has been running, start with `kilobat dns fastest --json` (CLI 0.29; MCP `get_fastest_dns`): runs on several days on this network, so it is far better evidence than one benchmark. `state` is `learning` until 3 different days have runs, then `network` (the network's own DNS is fastest or nothing beat it clearly) or `faster` with `choice`, `choiceMs` against `networkMs`. `penalized` lists resolvers whose CDN answers connect clearly slower, which make pages slower despite faster lookups; `networkRewritesMissing` means the network's DNS invents answers for names that don't exist.

Newer than CLI 0.33, each resolver also has `label`, `runBy`, `entity` and `jurisdiction`: who runs it and the country it's established in ("Quad9 · Switzerland", "Cloudflare · United States"), from operators' own pages. The network's own DNS is "Your provider’s" and an address Kilobat doesn't know is "Unknown operator", with `jurisdiction` null: say so, and don't guess a jurisdiction from the address. `history` holds each resolver's `answered`, `failed` and `slow` lookups (slower than `slowMs`) in the runs of the last 14 days with a `successRate`; a resolver that is fast but fails a few percent of lookups is a worse choice than a slightly slower one that answers everything. `fallback` is the second resolver the user picked (null if none), and `applied.fallback` is true while Kilobat is on it because the fastest failed.

For one quick sample, run `kilobat dns-benchmark`. It prints JSON (no `--json` flag): one entry per resolver with `resolver` (`System`, `1.1.1.1` for Cloudflare, `8.8.8.8` for Google, `9.9.9.9` for Quad9), `milliseconds` (null if none answered) and `replies`, out of three test domains.

- Run it twice. Treat a resolver as faster only if it wins both runs by a clear margin, roughly 20 ms or more. Single-digit differences are noise.
- Fewer `replies` than the others means lost queries, which hurts more than a few milliseconds.
- If the system resolver is the router (a private address such as 192.168.x.x), a slow result may be the router itself.

## 4. Separate DNS from the site

For "one site is slow", run `kilobat http-check https://example.com --json` with the site's URL. It returns the HTTP `status` and cumulative `dnsMs`, `connectMs`, `tlsMs`, `firstByteMs` and `totalMs`. A large `dnsMs` points here; a large gap between `tlsMs` and `firstByteMs` is the server, not DNS. Compare against a second site before blaming DNS.

## 5. Change DNS, with approval

Name the change, the reason with numbers, and how to undo it, then wait for a yes.

- `kilobat dns cloudflare`, `kilobat dns google` or `kilobat dns quad9` sets that provider on the active network service. `kilobat dns automatic` returns to the network's own DNS.
- `kilobat dns flush` clears the macOS DNS cache. It helps after a site moved or a stale "server not found"; it does not make DNS faster.
- To have the app pick the fastest DNS per network and switch on joining (Pro, CLI 0.29): `kilobat dns auto on` for every network or `kilobat dns auto on --network "<name>"` for one; MCP `set_fastest_dns`. It never switches while a VPN, a configuration profile or a Wi-Fi sign-in page manages DNS, never over servers the user set, and puts automatic DNS back when lookups fail. `kilobat dns exclude google` keeps one out.
- To give it a second resolver for when the fastest fails (newer than CLI 0.33): `kilobat dns fallback quad9` (or cloudflare, google, an IP address; `off` for none); MCP `set_dns_fallback`. The app moves to the fallback only if it answers right then, and puts automatic DNS back if the fallback fails too. Mention who runs the fallback and where before setting it.
- Other providers cannot be set by the CLI. The user sets them in System Settings › Network › the service › Details › DNS, or uses an encrypted DNS profile (below).
- Encrypted DNS: `kilobat dns-profile https://dns.example/dns-query > Kilobat-DNS.mobileconfig` writes a DNS-over-HTTPS configuration profile for the given HTTPS endpoint, for example `https://cloudflare-dns.com/dns-query` or `https://dns.quad9.net/dns-query`. The user reviews and installs it in System Settings; removing the profile restores the previous behavior.

Things to warn about before changing:

- Corporate networks and VPNs often need their own DNS for internal names. `kilobat interfaces --json` shows whether a VPN is up; if one is, do not change DNS without the user checking with their admin.
- A custom resolver or encrypted DNS profile can hide captive portal pages on hotel and café Wi-Fi.
- Parental controls or ad blocking on the router stop working when the Mac bypasses the router's DNS.

## When the cause isn't clear: look up a guide

Kilobat's site has guides for common macOS networking problems and step-by-step recipes, with sources and the macOS versions they apply to. When the measurements don't point to a cause, or the symptom is a known macOS pattern (Wi-Fi drops after sleep, Private Relay breaking a site, a container that can't reach localhost), fetch `https://kilobat.app/guides/index.json` once. Match the user's words and what you measured against each entry's `title`, `searches` and `symptoms`, and check `appliesTo` against the Mac's macOS version. Open the best match's `url`, follow its checks before its fixes, and give the user the link. A guide is general advice: prefer what you measured on this Mac, and still ask before any change.

## 6. Verify

Run `kilobat diagnose --json` and `kilobat dns-benchmark` again and report before and after, including `dnsServers`. If nothing improved, offer to restore the original setting (`kilobat dns automatic`, or the servers recorded in step 2) and look elsewhere with `mac-network-troubleshooting`.

Wersje

W bazie nie ma innych skilli o nazwie mac-dns-troubleshooting.

Migawka bazy z 13.11.2026 · wersja paczki f3bc394c4ccd (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100mac-network-troubleshooting
    Diagnozuje wolny lub zawodny internet na Macu: mierzy sygnał, opóźnienia, utratę pakietów i DNS, a potem proponuje jedną poprawkę.
  • 100cloudflare-dns
    Zarządza rekordami DNS w Cloudflare narzędziem flarectl: wyświetla, dodaje, aktualizuje i usuwa rekordy oraz pobiera informacje o strefie.
  • 95cloudflare-dns
    Prowadzi zarządzanie DNS w Cloudflare z integracją Azure: Cloudflare jako autorytatywny DNS, rekordy przez API, tokeny API, proxy, rozwiązywanie problemów, bezpieczeństwo DNS i External-DNS dla Kubernetes.
  • 100external-dns
    Prowadzi konfigurację i diagnostykę External-DNS dla Azure DNS, AWS Route53, Cloudflare i Google Cloud DNS, z uwierzytelnianiem, wydajnością i limitami zapytań.
  • 100cloudflare-dns
    Opisuje DNS Cloudflare: anycastowy DNS autorytatywny, tryb proxy i DNS-only, DNSSEC, Foundation DNS, resolver 1.1.1.1, DNS Firewall, secondary DNS, spłaszczanie CNAME i zarządzanie przez API oraz Terraform.
  • 96cloudflare
    Zarządza strefami DNS, pamięcią podręczną, tunelami i Workers w Cloudflare przez API.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.