macOS 26 breaks custom DNS settings including .internal

An overnight macOS 26 update just turned a bunch of developers’ “myapp.internal” test sites into pumpkins, and the comments are pure chaos. Users say Apple’s DNS helper now hijacks any made‑up domain ending (like “.internal” or “.test”) and treats it like a local network shout instead of asking your own DNS server—so nothing resolves, and work grinds to a halt. The bug report is up on Apple’s Feedback Assistant here, but the pitchforks are already out.

The loudest vibe: “Apple broke my setup and didn’t tell anyone.” One user called the whole thing “amateur,” claiming even Screen Time is stepping on ports and breaking Docker builds. Another camp says: this is on you—old‑school devs point out the easy “/etc/resolver” trick was flagged as deprecated years ago, and the “proper” (if clunky) route is Apple’s “scutil” tool. Then there’s the hardware‑versus‑software drama: one commenter loves Apple chips but wants the company split in two because they “will never use” the OS.

And the memes? Absolute gold. People joked that “.internal just got personal,” that “mDNS now stands for ‘my DNS now’,” and that the bizarre 108,002‑second cache time is “how long we’ll wait for a fix.” Adding fuel, someone called out a “macOS 25” slip in the write‑up and accused the bug report of being AI‑written. So is this a legit regression or Apple finally killing off a dusty feature? Either way, if your local sites vanished overnight, you’re not alone—and the internet has thoughts.