[dead]
macOS 26 breaks custom DNS settings including .internal
51–60 of 240 posts
Re: macOS 26 breaks custom DNS settings including .internal
#52Earlier quoted context omitted.
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.
There is a huge difference between using an llm and just blindly dumping it's output on someone verbatim. I think it's fine to have an llm write a first or second draft of something, then go through and reword most of it to be in your own voice.
The LLM presents a perverse incentive here - It is used for perceived efficiency gains, most of which would be consumed by the act of rewriting and redrafting. The alienness of the thoughts in the document is also non-condusive to this; Reading a long document about something you think you know but did not write is exhausting and mentally painful - This is why code review has such relatively poor results.
Quite frankly, while having an LLM draft and rewriting it would be okay, I do not believe it is reasonable to expect that to ever happen. It will be either like high school paper plagarism (Just change around some of the sentences and rephrase it bro), or it will simply not even get that much. It is unreasonable with what we know about human psychology to expect that "Human-Rewrites of LLM drafts", at the level that the human contributes something, are maintainable and scalable; Most people psychologically can't put in that effort.
Re: macOS 26 breaks custom DNS settings including .internal
#53[deleted]
Re: macOS 26 breaks custom DNS settings including .internal
#54Apple container CLI configures internal domains (`container system dns`) by adding an internal resolver and it worked for me when I specified an actual domain previously handled by external DNS and it showed up as a custom resolver.
Here’s a GitHub comment showing someone on MacOS 26 with a `.test` domain, which you claim is broken: https://github.com/apple/container/issues/856#issuecomment-3... —- maybe you are configuring it incorrectly.
Re: macOS 26 breaks custom DNS settings including .internal
#55It'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 python/wget/etc or any calls you make to getaddrinfo()
Re: macOS 26 breaks custom DNS settings including .internal
#56Honest question:
How would this affect me and the vast majority of macOS users who use the device for media consumption and productivity applications?
Next question: what reason would Apple have to make a change that would interfere with developers using their operating system?
Re: macOS 26 breaks custom DNS settings including .internal
#57Earlier quoted context omitted.
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.
> If you didn't take the time to compose your words thoughtfully then you aren't owed the time to read them. Apply this argument to code, to art, to law, to medicine. It fails spectacularly. Blaming the tool for the failure of the person is how you get outrageous arguments that photography cant be art, that use of photoshop makes it not art... Do you blame the hammer or the nail gun when the house falls down, or is i…
I of course expect my lawyer and doctor to thoughtfully apply their knowledge to help me. Why should they be any different?
Re: macOS 26 breaks custom DNS settings including .internal
#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?
Re: macOS 26 breaks custom DNS settings including .internal
#59Has anyone found a working workaround yet? I use dnsmasq for .local dev routing and held off updating after seeing this but curious if there is a viable path forward short of waiting for Apple to patch it.
holding off update seems like reasonable step till the patch comes. I also run a .local for apple containers though not docker.
[deleted]
Re: macOS 26 breaks custom DNS settings including .internal
#60Earlier quoted context omitted.
There’s no “Tahoe mess”. I’ve used it since 26.0 and it’s good. Different indeed, but good. People love complaining.
I'm glad that it's working well for you, but from the moment some users with M-series SoCs report laggy animations, something somewhere has to be wrong.
[deleted]