Live data from Hacker News

macOS 26 breaks custom DNS settings including .internal

gist.github.com

231–240 of 240 posts

Re: macOS 26 breaks custom DNS settings including .internal

#231

Earlier quoted context omitted.

I agree linux is just as bad, but at least I can fix it! Especially now in the age of AI I have fixed 30-40 issues with KDE that were bothering me and now they're gone. The reason why I don't upstream is because.. it's AI and half the changes are very opinionated. However, my enjoyment and productivity went up a lot. My KDE is closer to hyprland than anything and I love it.

I agree linux is just as bad, but at least I can fix it! I for sure see the appeal. Even if macOS desktop were open source, though, I doubt I'd do much about my complaints. For my use cases, I don't want to turn OS maintenance into a hobby, and whatever complaints I might have aren't big enough to go to the trouble to begin with. Bespoke user land does have its temptations, though. Maybe I'll finally get off my butt…

AI is a beast at figuring out the internals I picked up oh-my-pi from one of the posts on this site, it's cake compared to what it was even just a year ago.

Re: macOS 26 breaks custom DNS settings including .internal

#232

Earlier quoted context omitted.

I've run into resolvers that filter things like that to prevent dns rebinding attacks. And localhost (the hostname) does not work for CORS. Best option is probably to set dev.our-root-domain.com in /etc/hosts [1]: https://en.wikipedia.org/wiki/DNS_rebinding

Haven't had an issue yet, with a team scattered across US, Canada and UK. I'm sure it's possible - but so far we've been using this for about 3 years with no hiccups.

Definitely more common on corporate networks.

I guess most home users (remote employees) are probably either using their ISP's resolvers, or browser DoH (Dns-Over-HTTPS).

Re: macOS 26 breaks custom DNS settings including .internal

#233

Earlier quoted context omitted.

GP said they weren't okay with someone using an AI to check for grammatical errors. If they would be okay with using software to check for spelling errors, I'd be interested to know why they're making that distinction. And I'd like to know what they think of autocorrect, which at least on the iPhone uses an on-device LLM nowadays.

"AI" can mean anything with machine learning. Spellchecker can use some sort of machine learning too. But what people mean when they say "AI" is LLM chatbot. But a spellchecker highlights mistakes, it doesn't suggest to rewrite the text arbitrarily like an LLM chatbot. So I totally understand how you can be for one and not other By the way autocorrect on the iphone got worse recently, bunch of times it "corrected" th…

Wow, you’re arguing. What about predictive T9?

Re: macOS 26 breaks custom DNS settings including .internal

#234
post #201

Earlier quoted context omitted.

Today, literally today. My pihole updated, broke its own dns, stopped working, and broke dns for every device on my network.

PiHole is a Linux kernel now?

macOS ain’t kernel either, XNU is the kernel of macOS. what is it you are comparing.

Re: macOS 26 breaks custom DNS settings including .internal

#236
post #135
post #79

macOS 26 has to be the most breaking version so far, its problems and intended breaking changes making my app dev life so hard this year. Just to name a few: - Reference Presets no longer allow setting arbitrary SDR nits, making it impossible to natively unlock 1600nits of brightness on MacBook Pros or 2000nits on Studio Display XDR which breaks my Lunar app [0] (this seems to be intended, no idea what hurt Apple tha…

There are rumors iOS 27 will be a sort of Snow Leopard update with no new features [1]. Just bug fixes and performance improvements. Hopefully Apple will do the same for macOS 27. [1] https://www.macrumors.com/2026/03/15/ios-27-will-reportedly-...

> Just bug fixes and performance improvements.

So more bugs and no improvements, just like Google.

Re: macOS 26 breaks custom DNS settings including .internal

#237

Earlier quoted context omitted.

"AI" can mean anything with machine learning. Spellchecker can use some sort of machine learning too. But what people mean when they say "AI" is LLM chatbot. But a spellchecker highlights mistakes, it doesn't suggest to rewrite the text arbitrarily like an LLM chatbot. So I totally understand how you can be for one and not other By the way autocorrect on the iphone got worse recently, bunch of times it "corrected" th…

Wow, you’re arguing. What about predictive T9?

?

Re: macOS 26 breaks custom DNS settings including .internal

#238
post #163

Earlier quoted context omitted.

Cool, so just ignore documentation then. Problem solved for everyone.

I dont see how that solves anything.

* Projects can focus on code first, and do best-effort on docs for low cost * Most of us get reasonable quality documentation, much better than what some poor developer would turn out in spare moments * You are spared from the outrage of imperfect documentation

Re: macOS 26 breaks custom DNS settings including .internal

#239
"The long-established behavior of encrypted DNS protocol settings from a profile overriding non-VPN domain-specific DNS settings has been confirmed internally from macOS 15.7.1 to macOS 26.5.:

"You will continute [sic] to run into the behavior of Quad9 DoT overriding the per-domain DNS settings so long as the profile is installed."

— there we have it from "privacy friendly" (whilst sneaking out age checks) Apple.

Re: macOS 26 breaks custom DNS settings including .internal

#240
post #69

Papercuts like this are why I moved away from macOS. I will say, I don't love the use of LLMs to write these bug reports. It's probably fine if reviewed, but at least review for things like "worked on macOS 25", which obviously didn't exist. If that wasn't caught, how sure are you that the rest of the report is accurate? We all want the bugs fixed, but people are going to start throwing out the obviously LLM written…

Its my strong belief that using AI in any capacity which does not upfront state "the following content was generated by artificial intelligence" is never acceptable. In most situations, allowing an AI to wield your name gives off the scent of "My time is more valuable than yours, so I've automated writing to you." It is quite disgraceful. If your use-case would be materially harmed by an upfront disclosure of AI gene…

What does attributing to AI get you over if the content stays the same?
Post reply on HN