I suppose I'm lazy - I've always used /etc/hosts, but then again, I've never had use cases like those mentioned in the linked gist.
macOS 26 breaks custom DNS settings including .internal
111–120 of 240 posts
Re: macOS 26 breaks custom DNS settings including .internal
#112Earlier quoted context omitted.
That's very elitist and unfair to people who previously struggled to form their words but now have a better chance at doing so.
I disagree, because those aren't their words.
Re: macOS 26 breaks custom DNS settings including .internal
#113macOS 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…
Re: macOS 26 breaks custom DNS settings including .internal
#114It'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…
ArchiveBox now uses this feature by default in the latest version to finally offer unique per-snapshot domain isolation, so we can safely replay archived JS without risking compromise of your whole archive.
Such an awesome feature, the barrier to do this used to be prohibitively high but now it "just works".
Re: macOS 26 breaks custom DNS settings including .internal
#115Earlier quoted context omitted.
Using LLM is perfect for writing documentation which is something I always had problems with it.
As someone who has dealt with projects with AI-generated documentation... I can't really say I agree. Good documentation is terse, efficiently communicating the essential details. AI output is soooooooo damn verbose. What should've been a paragraph becomes a giant markdown file. I like reading human-written documentation, but AI-slop documentation is so tedious I just bounce right off. Plus, when someone wrote the do…
The choice is not usually “have humans write amazing top notch documentation, or use an LLM”.
The choice is usually “have sparse, incomplete, out-of-date documentation… or use an LLM”.
Re: macOS 26 breaks custom DNS settings including .internal
#116Re: macOS 26 breaks custom DNS settings including .internal
#117*.localhost works out of the box doesn’t it? You don’t need dnsmasq at all to have multiple hostnames pointing to 127.0.0.1.
If you just want to resolve 127.0.0.1 then you just resolve hostname "localhost" or use 127.0.0.1 directly.
Personally i don't bother configuring custom private dns zones, instead i use reserved MDNS *.local that autoconfigure everything using machine name (hostname) and DHCP address: somehostname.local in A .
Re: macOS 26 breaks custom DNS settings including .internal
#118I am not familiar with dnsmasq at all (is this machine-local?), but absolutely love my PiHole hardware — you can even create rules which intercept hard-coded-IP DNS request and/or httpsDNS. You can also hard-code/intercept .TLD to local service IPs. Programs like LittleSnitch never really seem like "enough" for me, because the computer has to boot before DNS filtering comes online. It also has the design error (IMHO)…
This works great (and I use it) internally but when you want things like your docker domains to work when you're on the go, it's annoying. I have setup a VM running DNS on my laptop before ...
There is a simple checkbox within the DNS's web interface to `Allow WAN Requests`. You'd then only run into issues of accessing your local IP addresses if those hosts aren't configured correctly within your network rulesets.
----
I am a user, not an expert; by trade, I am a blue collar electrician. I know very little about internet topology except how to use simple open-source hardware. Perhaps what you said makes sense (e.g. that you cannot use outside your network, some service(s)).
Re: macOS 26 breaks custom DNS settings including .internal
#119Earlier quoted context omitted.
(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.
There's a reason macOS is the least-used OS behind Linux and Windows. If it was any less terrible, we would know.
[1]: https://gs.statcounter.com/os-market-share/desktop/worldwide...