When a website loads on Windows but not on a Mac, the two computers are usually asking different DNS servers. DNS is the lookup system that turns a domain name like example.com into the server address a browser connects to. For site owners and marketers, this split result rarely means the site is down. It means one resolver has the current address and the other has an old, blocked, or private answer.
Table of Contents
- Why can two computers get different answers?
- Where do you find the real settings?
- What silently overrides DNS on a Mac?
- How do you compare them without guessing?
- Which fix matches the pattern you see?
- Frequently Asked Questions
Why can two computers get different answers?
Each device follows its own resolver chain. It checks its local hosts file, then its local cache, then the DNS servers assigned to its network connection. If any link differs, results differ.
Windows and Mac machines often pick up different servers without looking different. One may use the office router, the other may use a manually entered server, a VPN server, or a family filter. Corporate laptops and home Macs also add privacy relays or security software that change lookups.
Where do you find the real settings?
On Windows, open network adapter settings and run `ipconfig /all` to see the DNS servers listed for the active connection. Note every address, plus any VPN adapter that shows its own servers. Those addresses are the resolvers Windows actually asks.
On Mac, open System Settings, select Network, choose the active Wi-Fi or Ethernet service, then open Details and DNS. Also check VPN profiles, content-filter apps, and iCloud Private Relay settings, because each can override the listed servers. Compare the two lists side by side on the same network.
What silently overrides DNS on a Mac?
The Mac hosts file can send one domain to a staging server while Windows goes to production. A hosts file is a local text list that maps names to addresses, and it beats normal DNS. Check `/etc/hosts` for the problem domain, especially after a migration or redesign.
Cached answers cause the next most common split. macOS stores recent lookups through its lookup service, and browsers keep their own short cache too. A Mac that visited the site during a move or outage can keep showing the failure after Windows picks up the corrected record.
How do you compare them without guessing?
Put both computers on the same Wi-Fi network and test the same full address, including www versus non-www. Then compare the resolver answers directly instead of reloading the browser.
- Write down the DNS server addresses from Windows and Mac.
- Check each hosts file for the domain: Windows `C:\Windows\System32\drivers\etc\hosts`, Mac `/etc/hosts`.
- Query the same name from each machine with system tools and note the returned IP address.
- Flush caches, quit and reopen the browser, then test in a private window with extensions off.
- Temporarily set both machines to the same public resolver to see if the gap disappears.
Which fix matches the pattern you see?
If both machines return different IP addresses, fix the lagging resolver or record. Lower confusion comes from waiting out the old record lifetime, clearing the Mac cache, or removing a stale hosts entry. Site teams should also check for duplicate DNS zones at the registrar and host, which feed different answers to different resolvers.
If both return the same address but only Mac fails, the block sits past DNS. Check Mac firewall prompts, security software, parental controls, VPN routing, HTTPS filtering, and browser secure-DNS settings. Change one variable at a time, then retest the live page and one test file path.
Frequently Asked Questions
Does this mean the website is down?
No. If one device loads it, the server usually works. The other device holds a wrong address, a cached failure, or a local block.
Should I change DNS on both computers to the same server?
Use that only as a short test. It shows whether the assigned resolvers disagree. Keep permanent network settings as your network owner requires.
I just moved hosts. Why does the Mac show the old site?
The Mac likely stored the prior address in system or browser cache, or a hosts entry still points to the old server. Clear both caches and remove the test entry.
