What Is Smart Multi-Homed Name Resolution?
Smart Multi-Homed Name Resolution is a Windows networking feature designed to speed up DNS resolution. In a typical setup, when your computer needs to resolve a domain name, it queries a single DNS server and waits for a response. If that server is slow or unresponsive, there's a delay.
Microsoft's solution was Smart Multi-Homed Name Resolution. Instead of querying one DNS server at a time, Windows queries all available DNS servers across all network interfaces simultaneously. Whichever server responds first wins, and the rest are discarded. This reduces DNS resolution latency because you're always getting the fastest available response.
On paper, this sounds like a smart optimization. In practice, it's a privacy disaster for anyone using a VPN.
Why Smart Multi-Homed Name Resolution Causes DNS Leaks
When you connect to a VPN, your system gains a new virtual network adapter. Your VPN configures this adapter to use its own DNS servers. In a perfect world, all DNS queries would go through this VPN adapter.
But with Smart Multi-Homed Name Resolution enabled, Windows doesn't respect that preference. It sends DNS queries through all network interfaces — both the VPN adapter (secure) and your physical network adapter (insecure). Your ISP's DNS server often responds faster than the VPN's because it's physically closer, so it frequently "wins" the race.
The result: every DNS query is sent to your ISP's servers, even with a VPN connected. Your ISP can see and log every website you visit. Your VPN is effectively useless for DNS privacy.
This isn't a theoretical risk — it's the most common cause of DNS leaks we see on Windows machines. You can test your system right now with our DNS Leak Checker.
How to Check If This Affects You
Before applying the fix, verify that Smart Multi-Homed Name Resolution is causing your leak:
- Connect to your VPN and confirm it shows "Connected"
- Run our DNS Leak Checker
- If you see DNS servers belonging to your ISP alongside (or instead of) your VPN's DNS servers, you likely have this issue
- Open Command Prompt and run
nslookup example.com— note which DNS server handles the query
Fix Method 1: Group Policy Editor (Windows Pro/Enterprise)
The Group Policy Editor provides the cleanest way to disable Smart Multi-Homed Name Resolution. This method is available on Windows Pro, Enterprise, and Education editions. If you're using Windows Home, skip to Method 2 (Registry).
Step 1: Open Group Policy Editor
Press Win + R, type gpedit.msc, and press Enter. If you get an error saying the file isn't found, you're on Windows Home — use the registry method instead.
Step 2: Navigate to DNS Client Settings
In the Group Policy Editor, navigate through the left panel:
Computer Configuration → Administrative Templates → Network → DNS Client
Step 3: Disable Smart Multi-Homed Name Resolution
In the right panel, find the policy named "Turn off smart multi-homed name resolution." Double-click it. Select "Enabled" (yes, you're enabling the policy that turns OFF the feature). Click "OK."
Note: The wording can be confusing. Setting this policy to "Enabled" means you are enabling the disabling of Smart Multi-Homed Name Resolution. When this policy is "Enabled," the feature is OFF.
Step 4: Also Disable Parallel DNS Resolution (Windows 10 1903+)
In the same DNS Client folder, look for "Turn off smart protocol reordering" and enable it as well. In newer Windows 10 and Windows 11 versions, Microsoft renamed and split the multi-homed resolution into additional policies. Enabling both ensures complete coverage.
Step 5: Force Group Policy Update
Open Command Prompt as Administrator and run:
gpupdate /force
This applies the policy immediately without requiring a restart, though a restart is recommended for reliability.
Fix Method 2: Registry Editor (All Windows Editions)
This method works on all Windows editions including Windows Home. It achieves the same result as the Group Policy method by directly editing the registry.
Step 1: Open Registry Editor
Press Win + R, type regedit, and press Enter. Click "Yes" on the User Account Control prompt.
Step 2: Navigate to the DNSClient Key
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient
If the "DNSClient" key doesn't exist, create it: right-click "Windows NT" → New → Key → name it "DNSClient."
Step 3: Create the DisableSmartNameResolution Value
Right-click in the right panel → New → DWORD (32-bit) Value. Name it DisableSmartNameResolution. Double-click the new value and set it to 1.
Step 4: Add the Parallel Resolution Disable (Recommended)
In the same key, create another DWORD value named DisableParallelAandAAAA and set it to 1. This prevents Windows from sending parallel A (IPv4) and AAAA (IPv6) DNS queries, providing additional leak protection.
Step 5: Restart Your Computer
Unlike Group Policy changes, registry edits typically require a restart to take effect. Save your work and restart Windows.
Step 6: Verify the Fix
After restarting, connect your VPN and run our DNS Leak Checker again. You should now only see DNS servers belonging to your VPN provider, not your ISP.
Command Line Method (Quick Copy-Paste)
If you prefer a quick command-line approach, open Command Prompt as Administrator and paste these commands:
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient" /v DisableSmartNameResolution /t REG_DWORD /d 1 /f REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient" /v DisableParallelAandAAAA /t REG_DWORD /d 1 /f
Restart your computer after running these commands.
Combining This Fix with Other DNS Leak Protections
Disabling Smart Multi-Homed Name Resolution is a critical step, but it's not the only thing you should do to prevent DNS leaks on Windows. For comprehensive protection:
- Change your DNS servers to privacy-focused providers — see our Windows DNS leak fix guide
- Disable IPv6 to prevent IPv6 DNS leaks — see our IPv6 disable guide for Windows
- Flush your DNS cache after all changes:
ipconfig /flushdns
- Enable your VPN's kill switch
- For a complete overview, see our master guide on fixing DNS leaks