Understanding the Split DNS Mechanism in macOS Sequoia
Split DNS is a networking configuration that allows a single device to use different DNS servers for internal and external traffic. In enterprise environments, this ensures that devices on a corporate network resolve internal hostnames (like intranet.company.local) using an internal DNS server, while external requests go to public resolvers like Google DNS or Cloudflare.
In macOS Sequoia, this functionality is deeply integrated into the system’s network stack, particularly when connecting to Virtual Private Networks (VPNs). The operating system uses the scutil utility to manage these routing rules. However, recent updates have introduced stricter validation for DNS suffixes, which can sometimes cause misconfigurations where internal DNS servers are incorrectly tasked with resolving public domains.
If your Synology NAS or other internal DNS server does not have records for public internet domains, it will fail to resolve them. Instead of returning a "Server Not Found" error, macOS might hang indefinitely or return incorrect responses, breaking your ability to browse the web while connected to the internal network or VPN.
Identifying Symptoms of Misconfigured Split DNS
The most common symptom is the inability to load external websites such as google.com or github.com while remaining able to access internal resources like shared folders on a Synology drive. You may also notice that the Network Utility shows no errors, yet standard tools like ping or nslookup timeout for public IPs.
Another indicator is high latency during initial page loads. If your system attempts to query the internal DNS server first for every request, and that server times out before forwarding the query to an upstream resolver, you will experience significant delays. This behavior is distinct from general connectivity issues, as your internet connection itself remains active.
Diagnosing DNS Resolution with Terminal Commands
To confirm that split DNS is the culprit, you need to inspect how macOS is currently handling DNS queries. Open the Terminal application and run the following command to view the current DNS configuration:
scutil --dns
This command outputs a detailed list of all DNS servers configured on your system, along with their associated domains. Look for the section labeled search. If you see internal domain suffixes (e.g., local, internal, or your company’s domain) listed here, they are being prioritized for resolution.
You can test specific resolutions using the dig or nslookup commands. For example:
nslookup google.com
If the response comes from your internal Synology server’s IP address rather than a public resolver like 8.8.8.8, then split DNS is misconfigured. Note that scutil --dns output can be verbose; focus on the serverOrder and domains fields to understand the priority order.
Fixing Split DNS Issues via Network Preferences
The most straightforward fix involves adjusting the DNS settings directly within the macOS System Settings. Navigate to System Settings > Network. Select the active network interface, such as Wi-Fi or Ethernet, and click Details.
- Click on the DNS tab.
- Review the list of DNS servers. If you see multiple entries, ensure that public DNS servers (like 1.1.1.1 or 8.8.8.8) are present.
- If you are using a VPN client, check its specific settings. Many VPN clients automatically add internal DNS servers to the system configuration upon connection.
- Try removing the internal DNS server temporarily to test if external browsing resumes. If it does, the issue is confirmed to be the internal server’s lack of public zone data.
For users who cannot remove the internal DNS due to policy requirements, you may need to adjust the Search Domains field. Removing unnecessary suffixes from this field can prevent macOS from querying the internal server for public domains.
Advanced Fix: Using scutil to Manually Clear DNS Cache
Sometimes, simply changing settings in the GUI is not enough because macOS caches DNS configurations aggressively. You can force a refresh of the DNS service using the Terminal.
sudo killall -HUP mDNSResponder
This command sends a hangup signal to the mDNSResponder process, which handles DNS resolution on macOS. It effectively clears the cache and forces the system to re-evaluate its DNS servers. After running this command, try loading a website again.
If the problem persists, you may need to manually edit the DNS configuration using scutil. Be cautious with this method, as incorrect syntax can disrupt network connectivity entirely. A safer alternative is to reset the network configuration by forgetting the network and reconnecting, or by deleting the network preferences plist file after backing it up.
Preventing Future Conflicts
To avoid recurring issues, ensure that your internal DNS servers are properly configured to forward unresolved queries to upstream public servers. If you are managing a Synology NAS, verify that the DNS Forwarder settings are enabled and pointing to reliable public resolvers. This way, even if macOS routes a public query to the internal server, it will successfully resolve it by forwarding the request.
Additionally, keep your VPN client updated. Developers frequently patch bugs related to DNS leak prevention and split tunneling in newer versions. If you continue to experience issues, consider consulting our guide on MacOS: Split DNS Not Working as Intended with VPN Profile for more advanced troubleshooting steps involving profile management.
Frequently Asked Questions
Why does my Mac resolve internal IPs for public websites?
This happens when the internal DNS server is configured as the primary resolver for search domains that include public suffixes. The Mac queries the internal server first, which lacks the public records and returns an error or timeout instead of forwarding the request.
How do I clear the DNS cache on macOS Sequoia?
Open Terminal and run sudo killall -HUP mDNSResponder. This command restarts the DNS responder daemon, clearing any stale or incorrect cached entries that might be causing resolution failures.
Can I use both internal and public DNS servers simultaneously?
Yes, but you must configure them correctly. Add the public DNS servers to the main DNS list and use the Search Domains field to specify which domains should be resolved by the internal server. This ensures external queries bypass the internal server.
What if the issue started after updating macOS?
Updates often reset network preferences or change how DNS policies are applied. Check if new VPN profiles were installed automatically. Reverting to a known good network configuration or resetting network settings can help restore previous functionality.
Is it safe to delete firewall rules to fix DNS issues?
No, deleting firewall rules is unrelated to DNS resolution and can compromise your security. While we have guides on deleting firewall rules on macOS 15, this should only be done if you are specifically troubleshooting blocked ports, not DNS lookup failures.