How To Fix Temporary Failure In Name Resolution On WSL2

In this step-by-step guide, we will address the “temporary failure in name resolution” issue that may occur when using Windows Subsystem for Linux 2 (WSL 2).

We will provide detailed instructions for each solution, ensuring a seamless development experience with WSL 2.

Understanding The Problem “Temporary Failure In Name Resolution” On WSL2

The “temporary failure in name resolution” error occurs when WSL 2 is unable to resolve domain names, causing difficulties when accessing external resources, such as downloading packages or connecting to remote servers.

This problem is typically caused by misconfigurations in network settings, issues with the virtual network adapter, or conflicts with Windows Fast Startup.

How To Fix Temporary Failure In Name Resolution On WSL2

Solution 1: Restarting Networking Services

Restarting the networking services within WSL 2 can help resolve the issue. Follow these steps:

• Open the WSL 2 terminal by searching for “WSL” in the Windows search bar.
• Enter the following command to restart networking services:

sudo service networking restart

• Test the connection by pinging a domain, such as google.com:

ping google.com

If the issue persists, proceed to the next solution.

Solution 2: Updating WSL 2 Configuration

Updating the WSL 2 configuration file can resolve the issue. Follow these steps:

• Open the WSL 2 terminal.
• Create or open the /etc/wsl.conf file using a text editor, such as nano:

sudo nano /etc/wsl.conf

• Add the following lines to the file:

[network] 
generateResolvConf = false

• Save and close the file.
• Restart WSL 2 by closing the terminal and reopening it.
• Test the connection using the ping command.

Solution 3: Modifying DNS Settings

Updating the DNS settings within WSL 2 can help resolve the issue. Follow these steps:

• Open the WSL 2 terminal.
• Edit the /etc/resolv.conf file:

sudo nano /etc/resolv.conf

• Replace the existing content with the following lines:

nameserver 8.8.8.8 
nameserver 8.8.4.4

These are the Google Public DNS addresses. You may also use other DNS servers, such as OpenDNS or Cloudflare, if preferred.

• Save and close the file.
• Test the connection using the ping command.

Solution 4: Disabling Windows Fast Startup

Windows Fast Startup can cause conflicts with WSL 2 networking. Disabling it may resolve the issue. Follow these steps:

• Right-click the Start button and select “Power Options.” 2. Click “Choose what the power buttons do” on the left side of the window.
• Click “Change settings that are currently unavailable” to enable editing.
• Uncheck the “Turn on fast startup (recommended)” option under “Shutdown settings.”
• Click “Save changes” and close the window.
• Restart your computer to apply the changes.

After disabling Windows Fast Startup, open the WSL 2 terminal and test the connection using the ping command.