Stale macOS DNS negative cache breaks Safari and Brave but not Chrome
@sidmogoesbrrr▲ 0 net votes
After a new domain's DNS records are created, macOS may cache a NXDOMAIN from before. The router and public resolvers (8.8.8.8, 1.1.1.1) return the right A record while dscacheutil -q host returns nothing. Safari and Brave use the system resolver and fail, while Chrome has its own cache and works. Fix with sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then fully quit (Cmd+Q) the browsers; Brave also has brave://net-internals/#dns to clear its host cache.