Local DNS Failure Can Look Like a Dead Server
Test the known address before rebooting a host just because its name stopped resolving.
DNS
mDNS and Tailscale Fail in Different Ways
A .local name and a Tailscale peer can refer to the same host while depending on different discovery systems.
DNS SRV Made SIP Service Discovery Feel Less Hard-Coded
Using DNS SRV records showed me how SIP clients can discover service hosts and ports without baking one server address into every configuration.
Using `dig` to Stop Treating DNS Like a Black Box
`dig` gave me a way to separate resolver configuration, authoritative answers, record types and response timing instead of reducing DNS to 'name works' or 'name fails'.
Ping Works but the Browser Does Not: Separating IP, DNS and Applications
Connectivity tests become useful only when each test is tied to a layer: local addressing, routing, DNS resolution, TCP reachability and the application itself.
Split-Horizon DNS: One Hostname, Two Network Paths, and a Lot of TLS Confusion
The same hostname can resolve to a local reverse proxy on LAN and a Cloudflare Tunnel externally. That is clean when DNS, SNI, certificates, and origin routing agree—and maddening when one layer quietly takes the other path.
DNS Lookup Time Belongs in an Edge Dashboard
A slow public request is not always slow application code; DNS resolution can consume a meaningful part of the user-visible path.
Working DNS Does Not Mean the Application Is Healthy
Resolving a domain to an address is an important first step, but DNS cannot tell you whether the service is reachable, the certificate matches, or the application itself is working. Successful name resolution is not system health.