Accessing a Windows DNS server from MacOS Sonoma typically fails due to network segmentation, firewall restrictions, or incorrect resolver configuration. To resolve this, verify that the MacOS machine can ping the Windows host, ensure the Windows Firewall allows DNS traffic on UDP/TCP port 53, and configure MacOS to use the Windows IP as a primary or secondary DNS server in Network Preferences.
Verifying Network Connectivity
The first step in troubleshooting any DNS issue is to establish basic network connectivity between the client and the server. MacOS Sonoma may have strict network isolation settings, especially if you are on a guest Wi-Fi network or a segmented corporate VLAN. You must confirm that your Mac can physically reach the Windows machine at the IP address level before worrying about DNS resolution protocols.
Open the Terminal application on your Mac and use the ping command followed by the IP address of your Windows DNS server. For example, if your server is at 192.168.1.10, type ping 192.168.1.10. If you receive replies, the network path is open. If the request times out, check your physical connection, Wi-Fi settings, or router configurations to ensure both devices are on the same subnet or that routing rules exist between them.
Configuring DNS Resolvers in MacOS
Once connectivity is confirmed, you need to instruct MacOS Sonoma to send DNS queries to the Windows server instead of relying solely on DHCP-assigned resolvers or public DNS like Google's 8.8.8.8. This is done through the System Settings interface. Navigate to System Settings > Network and select your active connection, whether it is Wi-Fi or Ethernet.
Click on Details next to your connection, then select the DNS tab. Here, you will see a list of existing DNS servers. Click the + button to add the IP address of your Windows DNS server. It is advisable to place this new entry above any existing entries so that MacOS attempts to query the Windows server first. Click OK and then Apply to save the changes. This configuration ensures that all domain name lookups are directed to your Windows environment.
Adjusting Windows Firewall Rules
A very common reason for failure is that the Windows Server operating system blocks incoming DNS requests by default, particularly if it is not configured as a primary Domain Controller or if advanced security policies are enabled. The Windows Firewall often restricts inbound traffic on port 53 to prevent unauthorized resolution services.
To fix this, log into the Windows server and open Windows Defender Firewall with Advanced Security. Create a new Inbound Rule for port 53. Select Port, then TCP and UDP, and specify port 53. Allow the connection for all profiles (Domain, Private, Public) and give the rule a descriptive name such as "Allow DNS Inbound". This action explicitly permits MacOS machines to send queries to the server without being dropped by the firewall.
Clearing MacOS DNS Cache
MacOS maintains a local DNS cache to speed up resolution times, but this can sometimes hold onto stale or incorrect data even after you change your server settings. If you have updated your DNS configuration but still cannot resolve domains via the Windows server, you must flush the local cache. This forces MacOS to re-query the newly configured Windows DNS server immediately.
In the Terminal, execute the command dscacheutil -flushcache; sudo killall -HUP mDNSResponder. You may be prompted for your administrator password. After running this, test your resolution by pinging a known internal hostname. If you encounter issues with other network services while configuring custom resolvers, refer to Configuring macOS with Custom DNS Resolvers in /etc/resolver for more granular control over domain-specific routing.
Testing and Troubleshooting Resolution
After applying these changes, use the nslookup or dig command in Terminal to verify that queries are actually reaching the Windows server. For instance, run nslookup example.com and observe the "Server:" line in the output. It should display the IP address of your Windows DNS server, not a public ISP resolver. If it shows a different server, your MacOS configuration was not saved correctly or another network interface is overriding it.
If you are using remote access tools to manage the Windows server from your Mac, ensure that the underlying virtualization or RDP setup does not interfere with local network traffic. Issues with remote apps blocking local network discovery are documented in Seamless Running of Remote Windows 11 Apps on MacOS using a Remote VM with VirtualBox or QEMU over Local Network with RDP. Always verify that your DNS server logs show incoming queries from your Mac's IP address to confirm successful communication.
Frequently Asked Questions
Why does my Mac still use Google DNS after I added the Windows server?
This usually happens because the Windows DNS server is listed below existing entries in the DNS panel. MacOS prioritizes the topmost server in the list. Move your Windows server IP to the very top of the list in Network Preferences and click Apply. Additionally, ensure no other network service like a VPN is overriding your settings.
Can I access the Windows DNS server if it is on a different subnet?
Yes, provided that routing exists between the subnets and the Windows Firewall allows inbound traffic from the Mac's subnet. You must also ensure that the Windows DNS service is bound to the correct network interface IP that is reachable from the Mac. Test connectivity with ping first to rule out routing issues.
What if I get a timeout error when pinging the Windows DNS server?
A timeout indicates a network-level blockage rather than a DNS configuration error. Check for active firewalls on intermediate routers, ensure both devices are on compatible network segments, and verify that the Windows server has an active network cable or valid Wi-Fi connection. If the server is behind a NAT gateway, you may need to set up port forwarding for UDP/TCP 53.
Does MacOS Sonoma support IPv6 DNS queries to Windows Servers?
Yes, MacOS fully supports IPv6 DNS resolution. If your Windows DNS server has an IPv6 address, you can add it to the DNS list in Network Preferences alongside the IPv4 address. Ensure that your network infrastructure supports IPv6 routing and that the Windows Firewall is configured to allow IPv6 inbound traffic on port 53.
How do I revert to automatic DNS if the Windows server becomes unavailable?
You can configure fallback DNS servers by adding additional IPs in the DNS tab of Network Preferences. Place the Windows server IP first, followed by a reliable public DNS like 8.8.8.8 or your router's IP. If the Windows server times out, MacOS will automatically attempt the next server in the list, ensuring continuous internet access.