Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS 26 breaks custom DNS settings including .internal

gist.github.com

Post reply on HN
Print view View original

71–80 of 240 posts

Re: macOS 26 breaks custom DNS settings including .internal

#71

Post by mikestew »

lysace wrote: post #58

> Ah, the joys of waking up to find the Mac's done an overnight upgrade Wait, it does that (from 15 to 26) without user interaction?

No, it does not. It’ll bug the shit out of you to upgrade, but it won’t automatically do a major version upgrade. By default it will automatically do minor version upgrades (that can be turned off).

That’s what makes the LLM bug report make no sense in light of OP’s report here. Bug says it’s a regression from 25.x (which doesn’t exist), so maybe they mean 15.x? But OP says they “woke up” and it was upgraded and broken, but macOS doesn’t major version upgrades w/o user action. So which is it?

Re: macOS 26 breaks custom DNS settings including .internal

#72

Post by zamadatix »

philo23 wrote: post #55

It's not quite the same, but I've moved to using *.localhost for all my local web dev work. All modern browsers will resolve *.localhost to 127.0.0.1 internally. No need to setup any DNS resolvers or edit your hosts file. But that only really helps you when you're dealing with websites in a browser, and when you want the address to resolve back to your local machine. So it wont help you with other programs like pytho…

Good tip, I didn't realize the browser would automatically resolve any subdomain of localhost to 127.0.0.1/::1 as well these days.

I tested on Chrome but I assume this is true for Safari as well?

Re: macOS 26 breaks custom DNS settings including .internal

#73

Post by himata4113 »

t-sauer wrote: post #12
himata4113 wrote: post #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.

But you can run your own kernel on Macs, no? Isn‘t driver support the issue?

Not on new silicon and asahi linux is still pretty damn far from being able to use it seriously. I do appreciate the effort, but I am just saying that it would be a lot better if you know, apple sold the hardware so vendors could build laptops with apple silicon.

Re: macOS 26 breaks custom DNS settings including .internal

#74

Post by mrpippy »

bgentry wrote: post #7
adamamyl wrote: 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 :)

The report says it broke when updating from macOS 15 to 26, so not a minor patch update. I'm a bit surprised no one noticed this earlier though, since 26 has been out since September and in beta since June.

Re: macOS 26 breaks custom DNS settings including .internal

#75

Post by himata4113 »

mikestew wrote: post #43
himata4113 wrote: post #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.

(arguably terrible) operating system macOS has made some arguably poor design choices, but it makes it hard to take someone seriously when they state the whole OS is terrible.

It could be just me, but every time I tried to do something I sat thinking that I am not the target audience for this thing. I don't like the UI, I hate not being able to talk to the hardware the way I can on linux (uart took me way too long to get working), I am angry that I am not able to run kvm, I hate not being able to replace the desktop and fix bugs myself. That's what makes it terrible for me.

Re: macOS 26 breaks custom DNS settings including .internal

#76

Post by lysace »

mikestew wrote: post #71
lysace wrote: post #58

> Ah, the joys of waking up to find the Mac's done an overnight upgrade Wait, it does that (from 15 to 26) without user interaction?

No, it does not. It’ll bug the shit out of you to upgrade, but it won’t automatically do a major version upgrade. By default it will automatically do minor version upgrades (that can be turned off). That’s what makes the LLM bug report make no sense in light of OP’s report here. Bug says it’s a regression from 25.x (which doesn’t exist), so maybe they mean 15.x? But OP says they “woke up” and it was upgraded and brok…

Phew.

Re: macOS 26 breaks custom DNS settings including .internal

#77

Post by philo23 »

zamadatix wrote: post #72
philo23 wrote: post #55

It's not quite the same, but I've moved to using *.localhost for all my local web dev work. All modern browsers will resolve *.localhost to 127.0.0.1 internally. No need to setup any DNS resolvers or edit your hosts file. But that only really helps you when you're dealing with websites in a browser, and when you want the address to resolve back to your local machine. So it wont help you with other programs like pytho…

Good tip, I didn't realize the browser would automatically resolve any subdomain of localhost to 127.0.0.1/::1 as well these days. I tested on Chrome but I assume this is true for Safari as well?

Just tried it on my Mac and sadly it doesn’t seem like it. I’m still on Sequoia, so possibly it does it on Tahoe, but probably unlikely. That’s a shame.

It’d be nice if someone on the Safari team added this though to match Chrome and Firefox!

Re: macOS 26 breaks custom DNS settings including .internal

#78

Post by yearolinuxdsktp »

duped wrote: post #16
mrbuttons454 wrote: post #13

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…

Using LLMs for any kind of writing is unethical, with the narrow exception of translation. If you didn't take the time to compose your words thoughtfully then you aren't owed the time to read them.

I disagree with the downvotes, but let me put it differently: if you don’t understand, have reviewed and be ready to own all of LLM output (the thoughtful part), then you aren’t owned the time to read them. If you didn’t try to reign in the verbose slop that’s the default for LLMs, I don’t want to read it.

Maybe the poster is running a local LLM.. you’d think that a SOTA model would have surmised that an overnight MacOS upgrade can only be a minor version.

Re: macOS 26 breaks custom DNS settings including .internal

#79

Post by alin23 »

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 that they had to block this under SIP)

- The orange microphone dot indicator and its very colored friends can no longer have their brightness changed for dimming them, which made my YellowDot app useless [1] (I guess this is for privacy, I still think this could have a setting guarded under TouchID like Accessibility Permissions works)

- Floating non-titled windows don't accept mouse events (thankfully this got fixed) [2]

- Gamma table changes don't work on MacBook Neo and M5 Pro/Max which breaks Sub-zero Dimming and dimming external monitors that don't support DDC (thankfully, Apple is looking into it) [3]

- The resizing area thing on very rounded windows which drives everyone nuts, I had to add custom resize handlers to some of my windows

- The `com.apple.SwiftUI.Drag-` temporary file paths that get generated for any file that gets dragged from a drag&drop handler which makes it impossible to get to the original file when dragging images from Clop [4] or file shelf apps like Yoink, Dropover etc.

- NSImage returning different pixel count for .size than what the image actually has, breaking workflows that depended on that to determine the image DPI

[0] https://lunar.fyi/#xdr

[1] https://github.com/FuzzyIdeas/YellowDot/issues/18

[2] https://developer.apple.com/forums//thread/814798

[3] https://developer.apple.com/forums/thread/819331

[4] https://lowtechguys.com/clop

Re: macOS 26 breaks custom DNS settings including .internal

#80

Post by stock_toaster »

whalesalad wrote: post #70
philo23 wrote: post #55

It's not quite the same, but I've moved to using *.localhost for all my local web dev work. All modern browsers will resolve *.localhost to 127.0.0.1 internally. No need to setup any DNS resolvers or edit your hosts file. But that only really helps you when you're dealing with websites in a browser, and when you want the address to resolve back to your local machine. So it wont help you with other programs like pytho…

we have dev.our-root-domain.com in public DNS pointing to 127.0.0.1

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

Post reply on HN