TELEMETRY // Normal: UDP/53 response < 30 ms | Fault: `ping 1.1.1.1` succeeds, `nslookup example.com` times out
Why It Happens: Residential routers advertise ISP default DNS servers via DHCP that frequently suffer regional outages or UDP packet drops even while the fiber/cable Layer-3 link remains completely healthy.
Fast Verification Test: Run `nslookup cloudflare.com 1.1.1.1`—if that resolves instantly while plain `nslookup cloudflare.com` fails, your default DNS server is dead.
Tools Needed: Windows Command Prompt or macOS Terminal
- Open Wi-Fi Adapter DNS settings (Windows Settings → Network → Wi-Fi → Hardware properties → DNS assignment, or macOS System Settings → Wi-Fi → Details → DNS).
- Set IPv4 DNS to `1.1.1.1` and `8.8.8.8` (and IPv6 to `2606:4700:4700::1111`).
- Save and reload your browser tab.
⚠️ Safety Boundary: On corporate laptops using internal split-DNS domains, check with IT before overriding corporate Active Directory DNS.
TELEMETRY // Normal: Valid TTL A/AAAA records | Fault: Negative NXDOMAIN cached across browser + OS stub resolver
Why It Happens: Waking a laptop during captive-portal Wi-Fi handoff caches negative NXDOMAIN responses inside the OS stub resolver and Chromium's internal async DNS cache.
Fast Verification Test: Test opening a domain you have never visited before in an Incognito window.
Tools Needed: Administrator Command Prompt or macOS Terminal
- On Windows: run `ipconfig /flushdns && netsh winsock reset` as Administrator; on macOS: run `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`.
- In Chrome/Edge/Brave, visit `chrome://net-internals/#dns` and click "Clear host cache".
⚠️ Safety Boundary: Restart the computer after `netsh winsock reset` to reinitialize clean socket catalogs.
TELEMETRY // Normal: Default route -> 192.168.x.1 | Fault: Loopback DNS 10.x.x.1 / WFP filter blocking port 53
Why It Happens: When a WireGuard/OpenVPN app crashes or sleeps ungracefully, its virtual TUN interface leaves DNS pointed at an unreachable `10.x.x.1` private tunnel address.
Fast Verification Test: Run `ipconfig /all` (Windows) or `scutil --dns` (macOS) and check if DNS points to `10.x.x.x` or `100.x.x.x` while the VPN shows disconnected.
Tools Needed: VPN client UI or Network Connections panel
- Open the VPN client, connect cleanly to any server for 5 seconds, and click Disconnect so it restores your physical adapter DNS.
- Toggle off "Permanent Kill Switch" if you intend to browse off-VPN.
⚠️ Safety Boundary: Avoid deleting virtual network adapters manually before disconnecting inside the VPN app.
TELEMETRY // Normal: Valid WAN public IP | Fault: 169.254.x.x APIPA address or 0.0.0.0 WAN status on router
Why It Happens: Your Wi-Fi router broadcasts strong local 5 GHz radio signal inside the house, while the upstream fiber ONT or cable modem lost its ISP DHCP lease after a brief utility blink.
Fast Verification Test: Check if phones on the same Wi-Fi also fail, and look for an amber/red WAN globe LED on the router.
Tools Needed: Access to modem and router power plugs
- Unplug BOTH the ISP modem/ONT and your Wi-Fi router from wall power for 45 full seconds.
- Plug in the ISP modem/ONT FIRST and wait 2 minutes until its Online LED turns solid, then power on the Wi-Fi router.
⚠️ Safety Boundary: Do not press the recessed pinhole Factory Reset button—simply power-cycle the DC barrel plug.