Fix Steam Error 105: Steam Error Code 105: DNS Resolution Failure (Steam)
Steam Error 105 is a frequent network connectivity issue that manifests when the Steam client is unable to connect to the server or load web-based content like the Store, Community, or Profile pages. As a Senior IT Technician, I diagnose this specifically as a failure in the Domain Name System (DNS) resolution process, meaning your computer cannot translate Steam’s web addresses into the correct IP addresses to establish a connection.
🧐 Causes
- Unreliable or slow DNS servers provided by your Internet Service Provider (ISP).
- Corrupted Steam web browser cache or temporary cookies within the client.
- Incorrect Windows Proxy settings or interference from a VPN.
- Outdated DNS resolver cache on the local operating system.
- Firewall or antivirus software blocking the Steam client’s outgoing requests.

🔧 Fixes
- Change to Public DNS: Navigate to your Network and Sharing Center, right-click your active connection, and enter “Properties.” Select IPv4 and change your DNS servers to Google’s Public DNS (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1).
- Flush the DNS Cache: Open the Command Prompt as an Administrator and type
ipconfig /flushdns. Press Enter to clear the local cache of outdated or “poisoned” IP records. - Clear Steam Browser Data: Open the Steam client, go to “Settings,” select the “In-Game” or “Web Browser” tab (depending on your version), and click “Delete Web Browser Data” to wipe corrupted cache files.
- Disable Proxy Settings: Press the Windows Key, type “Proxy Settings,” and ensure that “Use a proxy server” is toggled to Off, as this often conflicts with Steam’s handshake protocol.
- Power Cycle Your Router: Unplug your modem and router for 30 seconds. This refreshes your ISP connection and can clear temporary routing table errors.
🚀 Summary
Steam Error 105 is almost always a configuration issue between your local network and the DNS server. To fix it quickly, prioritize flushing your DNS cache and switching to a reliable third-party DNS provider like Google or Cloudflare. If the issue persists, clearing the Steam client’s internal browser cache will usually resolve the remaining data conflicts.