HowToFixWiFiSimple fixes  •  Better connection
Troubleshooting and Repair

Why Is My Macbook Not Connecting to Wifi? mDNS Resolver Errors

Introduction If you are asking, “Why Is My Macbook Not Connecting to Wifi?” and you have noticed mDNS resolver errors in Console, system logs, or network diagnostics, the problem is usually not as mysterious as it first appears. On macOS, the mDNSResponder ser

HowToFixWiFi

Introduction

If you are asking, “Why Is My Macbook Not Connecting to Wifi?” and you have noticed mDNS resolver errors in Console, system logs, or network diagnostics, the problem is usually not as mysterious as it first appears. On macOS, the mDNSResponder service handles both ordinary DNS lookups and Bonjour-style multicast DNS. When that resolver becomes confused, your MacBook may show a Wi-Fi connection but fail to load websites, may fail to join a network at all, or may connect and disconnect repeatedly.

This guide explains what mDNS resolver errors are, why they happen, and how to troubleshoot them step by step. It is written for everyday Mac users as well as people who are comfortable using Terminal. You do not need to be a network engineer to follow most of the fixes, but a few advanced sections include commands that should be used carefully.

Table of Contents

What “Not Connecting to Wi-Fi” Really Means

When someone searches “Why Is My Macbook Not Connecting to Wifi?”, the phrase can describe several different problems. Your MacBook may not see any networks, may see networks but fail to join them, may join but show “No Internet,” or may connect and then drop the connection every few minutes. Each symptom points to a different layer of the network stack.

A Wi-Fi connection has at least four separate stages: radio connection, IP address assignment, DNS resolution, and application-level access. mDNS resolver errors usually appear after the Wi-Fi radio has connected but before websites load. In other words, your Mac may be successfully associated with the router while failing to translate domain names such as apple.com into IP addresses.

That distinction matters because rebooting the router will not always fix a resolver cache problem, and flushing DNS will not fix a weak wireless signal. Before making major changes, identify the exact symptom. Try loading a website by name and by IP address. If an IP address loads but a domain name does not, DNS or mDNS is strongly suspected.

What Is the mDNS Resolver on macOS?

macOS uses a background service called mDNSResponder for DNS resolution. Despite the name, it is not limited to multicast DNS. It handles standard unicast DNS queries, local hostname resolution, Bonjour service discovery, and certain system networking tasks. When an app asks for the IP address of a website, macOS often routes that request through this resolver.

The term “mDNS resolver errors” can refer to log messages from mDNSResponder, failed DNS lookups, timeout messages, or Bonjour-related failures. These errors may appear in Console, in network diagnostics, or in the output of commands such as scutil --dns. They do not always mean the service itself is broken. Sometimes the resolver is correctly reporting that a DNS server did not respond, a VPN changed routing, or a local hostname conflict exists.

Because mDNSResponder is central to macOS networking, restarting it can temporarily clear stale cache entries and reset resolver state. That is why many troubleshooting guides begin with flushing the DNS cache and restarting the service.

Common mDNS Resolver Errors and Symptoms

mDNS resolver problems can look different depending on macOS version, network hardware, and installed software. The following table summarizes common symptoms, likely causes, and the first action to try.

Symptom Likely Cause First Action
Wi-Fi connected, but websites do not load Stale DNS cache or bad DNS server Flush DNS and restart mDNSResponder
Domain names fail, but IP addresses load DNS resolver or DNS server issue Check scutil --dns and DNS settings
Mac joins network, then disconnects IP conflict, DHCP issue, or Wi-Fi interference Renew DHCP lease and restart router
Only one app cannot reach the internet Proxy, firewall, or app-specific network rule Check VPN, proxy, and firewall settings
Bonjour devices disappear from network Multicast DNS or local network issue Restart mDNSResponder and check router multicast settings
Console shows repeated mDNSResponder timeouts Unresponsive DNS server or network path issue Change DNS servers and test another network

Log messages may include words such as timeout, no response, name conflict, or resolver failure. A single timeout is not always serious. Repeated errors every few seconds usually indicate a persistent configuration or network problem.

Examples of Error Patterns

You may see patterns like these in Console or Terminal output:

mDNSResponder: ... timeout
mDNSResponder: ... no response from server
mDNSResponder: ... name conflict detected
mDNSResponder: ... resolver failure

These are examples of message styles, not exact strings guaranteed on every macOS version. The important clue is repetition. If the same error appears continuously while browsing, it is worth troubleshooting. If it appears once during sleep or wake, it may be normal.

Quick Checks Before Deep Troubleshooting

Start with simple checks. They solve many cases of “Why Is My Macbook Not Connecting to Wifi?” without changing system files.

  1. Turn Wi-Fi off and back on from the menu bar.
  2. Restart your MacBook.
  3. Restart the router and modem.
  4. Move closer to the router and test again.
  5. Forget the Wi-Fi network and reconnect.
  6. Test a different network, such as a phone hotspot.
  7. Check whether other devices can use the same Wi-Fi network.
  8. Disable VPN or proxy software temporarily.

If the problem happens on every network, including a hotspot, the issue is likely on the Mac. If it happens only on one router, the issue may be router configuration, DNS settings, or wireless interference.

Also check macOS updates. Network bugs are sometimes fixed in point releases. Go to System Settings, then General, then Software Update. If an update is available, install it before deeper troubleshooting.

Flush the DNS and mDNS Cache

Flushing the DNS cache is one of the safest and most useful first fixes for resolver errors. It removes stale entries that may point to old IP addresses or expired DNS records.

Open Terminal and run:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

The first command flushes the Directory Service cache. The second sends a hang-up signal to mDNSResponder, prompting it to reload. You may be asked for your administrator password. Terminal does not show characters while you type the password.

After running the commands, test browsing again. If the problem was a stale cache, websites should load immediately. If the commands fail because the service name differs on your macOS version, restart the Mac and test again. Do not repeatedly run the commands; once or twice is enough.

Restart or Reset mDNSResponder

If flushing does not help, you can restart the service more directly. In many cases, sudo killall -HUP mDNSResponder is sufficient. If the service does not respond, a full restart of the Mac is often safer than forcing repeated kills.

Advanced users can inspect the process with:

ps aux | grep mDNSResponder

This shows whether the process is running. If it is not running at all, macOS networking will be severely impaired. Restarting the Mac should restore it. If it repeatedly crashes, check for third-party networking software, kernel extensions, or VPN clients that may be interfering.

Avoid using aggressive commands to kill system processes unless you understand the consequences. macOS is designed to restart mDNSResponder automatically when needed, but repeatedly terminating it can create temporary instability.

Review Network Settings and DNS Servers

Bad DNS settings are a common cause of mDNS resolver errors. If your Mac uses custom DNS servers that are offline, slow, or blocked, name resolution fails even though Wi-Fi is connected.

Check your current resolver configuration with:

scutil --dns

This displays the DNS servers and search domains macOS is using. Compare those servers with what your router provides. You can also view and change DNS in System Settings under Network, then your Wi-Fi connection, then Details, then DNS.

For testing, try well-known public DNS servers such as:

  • 8.8.8.8 and 8.8.4.4
  • 1.1.1.1 and 1.0.0.1
  • Your router’s default DNS settings

Do not leave custom DNS in place if you do not need it. Start with automatic DHCP-provided DNS, then test public DNS only as a comparison. If public DNS works but your router’s DNS does not, the router or ISP may be the problem.

You can also reset DNS for the Wi-Fi interface using:

networksetup -setdnsservers "Wi-Fi" empty