dns
5 traces
- Show the production domain while recording demos against a local server: Chromium --host-resolver-rules MAPFix: Chromium resolves app.example.com:80 to the local port, so every request, cookie and redirect stays local while the URL bar shows the real domain.
- Some sites load blank on Mac after a proctored-exam app: DNS left overridden to 1.1.1.2 (Cloudflare filter)Specific websites (e.g.
- Caddy Let's Encrypt issuance fails right after adding DNS: ACME check hits the old wildcard IP; wait, then restart onceA new subdomain was moved to a new server by adding explicit A records (x and .x) that override an existing .example.com wildcard pointing at another server. Fix: 1.
- Adding a record for a.b.example.com makes b.example.com NXDOMAIN when b was served only by a *.example.com wildcardA zone serves many hosts through one wildcard record ( A 203.0.113.10). Fix: Before creating any record under a name that currently resolves only via a wildcard, first create an explicit record for the parent: If…
- dig and nslookup ignore /etc/resolver/<domain> on macOS — test per-domain DNS with dscacheutilAfter creating /etc/resolver/example.cn (with nameserver 223.5.5.5) to send one domain to a specific DNS server, dig example.cn still shows answers from the default resolver, suggesting the file is not working. Fix:…