DNS_ERROR_NO_DNS_SERVERS (0X0000267C) Fix – No DNS Servers Configured

What's the 0X0000267C Error?

This error means Windows can't find any DNS servers to use. DNS is like a phonebook for the internet – it turns website names like "google.com" into IP addresses. Without it, you can't browse the web. I've seen this on Windows 10 and 11 mostly when someone messed with network settings or after a bad update.

Cause #1: Network Adapter Is Set to Static DNS (That's Empty)

Most common cause. Some software or a user accidentally sets the DNS server fields to blank or zeros. Happened last month with a client who installed a VPN that borked their adapter settings.

Fix: Reset the adapter to automatic DNS

1. Open Control Panel > Network and Sharing Center > Change adapter settings.
2. Right-click your active network (Wi-Fi or Ethernet) > Properties.
3. Select "Internet Protocol Version 4 (TCP/IPv4)" > Properties.
4. Make sure both options are set to "Obtain DNS server address automatically".
5. If they're already automatic, switch to manual and enter 8.8.8.8 and 8.8.4.4 (Google's DNS) as a test.
6. Click OK and close all windows.

Quick command line version: Open PowerShell as admin and run:

netsh int ip reset
netsh winsock reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew

Then reboot. This resets everything back to defaults. I've used this on maybe 50 PCs and it works 9 times out of 10.

Cause #2: Router or Modem Is Not Handing Out DNS

Sometimes the router itself stops serving DNS. This happens after power outages or when the router's DHCP pool runs dry. I had a client last week whose entire office couldn't connect – the router was set to use a custom DNS server that went offline.

Fix: Reboot the router and check its DNS settings

1. Unplug your router and modem (if separate). Wait 30 seconds. Plug modem back first, then router.
2. Once it's back online, open a browser and log into your router's admin page (usually 192.168.1.1 or 192.168.0.1).
3. Look for DNS settings. Common spots: under WAN or Internet settings, or LAN > DHCP server.
4. Make sure it's set to "Obtain DNS automatically" or use public DNS like 8.8.8.8 and 1.1.1.1.
5. Save changes and reboot the router again.

Test after reboot: On your PC, run ipconfig /all and look for "DNS Servers". You should see something like 192.168.1.1 (your router) or 8.8.8.8.

Cause #3: Corrupted DNS Cache or Network Stack

Less common but happens. Windows stores recent DNS info in a cache. If it gets corrupted, your computer can't talk to any DNS servers. I've seen this after malware scans or failed Windows updates.

Fix: Clear DNS cache and reset network stack

1. Open Command Prompt as admin.
2. Run these one at a time:

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset

3. Reboot your PC. That's it.

If you still get the error, check if DNS Client service is running:

1. Press Win+R, type services.msc, hit Enter.
2. Find "DNS Client". Should be running and set to Automatic.
3. If stopped, right-click > Start. Also double-check it's not disabled.

Quick-Reference Summary Table

Most of the time, it's cause #1. I've fixed this error in under a minute on remote calls. If none of these work, try a different network cable or Wi-Fi – sometimes it's just a bad connection that stops DNS requests from getting through.