Live data from Hacker News

macOS 26 breaks custom DNS settings including .internal

gist.github.com

1–10 of 240 posts

macOS 26 breaks custom DNS settings including .internal

#1
One of those 'woke up to MacOS updates' and finding none of my dockers are reachable via dnsmasq (which I use), and low and behold, an update silently breaks custom dns resolution. Hopefully Apple will listen to the bug report I've made. Hold off on updating if you use this…

macOS 26 breaks custom DNS settings including .internal
gist.github.com

Re: macOS 26 breaks custom DNS settings including .internal

#6
If you have ScreenTime turned on. Port :8080 is occupied and your ubuntu apt-get in a docker build gets hash mismatch because they obviously modified packets. Let alone I am having another issue of unable to delete a private key in Keychain Access.

The whole macOS thing is amateur

Re: macOS 26 breaks custom DNS settings including .internal

#7
post #3

Before others jump in: I already use Linux (and used to run FreeBSD as my desktop operating system).

Thanks for sharing your report, it's frustrating to see things like this break in minor patch updates. Small tip for GitHub Gist: set the file format to markdown (give it a .md extension) so that the markdown will be rendered and won't require horizontal scrolling :)

Re: macOS 26 breaks custom DNS settings including .internal

#9
I run a setup like that on my (outdated) Yosemite machine to provide multiple private TLDs for local deployment/development needs.

I set that up in like 2014? Even back then it was known already that the quick /etc/resolver way was the deprecated way to do things. So I guess they finally killed that feature off?

The proper (more awkward) way is to use scutil directly (which then stores the settings in some binary plist somewhere, I assume).

Maybe try this and see if it still works afterwards?

Re: macOS 26 breaks custom DNS settings including .internal

#10
Still wishing for the day apple is split into the hardware and the software company. I want their silicon, but I will never use their (arguably terrible) operating system. If I can't run my own kernel and kernel modules then it's a device that I don't own. Firmware is alright in some cases, but my laptop next to me is running core boot just to prove a point.
Post reply on HN