macOS 26.3.1 Update Breaks /etc/resolver/ DNS Configuration for Custom TLDs
By
adamamyl
The bagel they save for the regulars. Don't skim, savour.
Summary
A detailed bug report documenting a regression in macOS 26.3.1 where the /etc/resolver/ mechanism for custom TLD DNS resolution has stopped working after an overnight update. The author describes the issue, provides technical details about the regression from macOS 25.x/26.3.0, and has filed an official feedback report with Apple. The content includes technical analysis of the DNS resolver mechanism that has been broken by the update.
Key quotes
· 5 pulledAh, the joys of waking up to find the Mac's done an overnight upgrade… and erm, suddenly things stop working.
The /etc/resolver/ per-domain DNS resolver mechanism — an Apple-documented, long-standing feature — appears to have been broken in macOS 26.3.1.
Product: macOS 26.3.1 (Darwin 25.3.0, Build 25D771280a)
Component: Networking → DNS / mDNSResponder
Regression from: macOS 25.x 26.3.0 (working immediately prior to overnight update)
You might also wanna read
AgentSwift: An Autonomous AI Coding Agent for Apple Platform Development
AgentSwift is a native macOS application that runs an autonomous AI coding agent specifically designed for Apple platform development. It us
github.com·1mo ago
Critical Bug in Claude AI: Misattribution of Self-Generated Messages to Users
The article discusses a critical bug in Claude (an AI assistant) where it sometimes sends messages to itself and then incorrectly attributes
dwyer.co.za·1mo ago
Critical macOS TCP Networking Bug Causes System Crashes After 49 Days of Uptime
Researchers discovered a critical bug in macOS TCP networking that causes system instability after exactly 49 days of uptime. The issue stem
photon.codes·1mo ago
Package Mate: Open-Source macOS Development Environment Manager for Apple Silicon
Package Mate is an open-source macOS development environment manager built in Go for Apple Silicon. It simplifies macOS dev setup by allowin
Product Hunt·1mo ago
Excel's Historical Bug: Why 1900 is Incorrectly Treated as a Leap Year
Microsoft Excel incorrectly treats the year 1900 as a leap year due to a historical compatibility decision. This bug originated from Lotus 1
Safehouse: macOS Kernel-Level Sandboxing for Secure Local AI Agent Development
Safehouse is a macOS-native sandboxing solution for local AI agents that provides kernel-level enforcement to prevent destructive actions. I
agent-safehouse.dev·2mo ago