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

Article summary

macOS 26 breaks custom DNS settings, including .internal, due to a change in how the operating system handles DNS queries for non-standard top-level domains. This affects developers who use custom DNS setups for local development and testing. The issue can be worked around by adding entries to /etc/hosts, but this is impractical for dynamic use cases. The problem has been reported to Apple and is currently unresolved.

Main themes

• macOS 26 DNS issues
• Custom DNS settings
• Developer workflows
• Apple software quality
• Operating system limitations

What commenters say

• The change in macOS 26's DNS handling is a significant regression that breaks established developer workflows.
• The issue is not a major problem and can be easily worked around by using alternative DNS setups or configurations.
• Apple's closed-source approach to software development makes it difficult for users to fix issues like this themselves.
• The problem is not unique to macOS and that other operating systems have their own set of issues and limitations.
• The use of custom DNS settings is a deprecated practice and users should adopt more modern approaches to DNS management.
• Apple's hardware is top-notch, but the company's software and operating system are not geared towards power users or developers.
• The ability to customize and fix issues in an operating system is a key factor in choosing a platform, with some preferring open-source options like Linux.
• The discussion around the issue highlights a broader debate about the trade-offs between ease of use, security, and customizability in operating system design.