How to persist your /etc/resolv.conf in WSL?

Recently, I found that whenever I restart WSL, the changes I made in /etc/resolve. conf are lost, and I need to configure it again manually. Finally, I found a way to persist /etc/resolv.conf in WSL. Big thanks to this post.

Firstly, Remove the /etc/resolv.conf:     

            `sudo rm /etc/resolv.conf`

And then, create a new /etc/resolv.conf:

          ` sudo bash -c 'echo "nameserver 8.8.8.8" > /etc/resolv.conf'`

And then, add an entry into /etc/wsl.conf

      `sudo bash -c 'echo "generateResolvConf = false" >> /etc/wsl.conf'`

Finally, 

         ` sudo chattr +i /etc/resolv.conf`

From now on, your /etc/resolv.conf will be persisted.

Enjoy it.


NOTES: chattr command is used to change the file or directory attributes. +i means "make the file immutable, it cannot be modified, delete, renamed, or linked"


        

Comments

Post a Comment

Popular posts from this blog

IPv4/IPv6 Dual-Stack in Kubernetes

 Today, I was asked by a teammate to help troubleshoot an issue related to dual-stack in Kubernetes. It turned out that I am quite so unfamiliar with this subject. Actually, I didn't know some very basic things about it.  Hence I spent some time studying it. This post is a summary of it. What is IPv4/IPv6 dual-stack? IPv4/IPv6 dual-stack networking enables the allocation of both IPv4 and IPv6 addresses to Pods and Services. IPv4/IPv6 dual-stack networking is enabled by default for the Kubernetes cluster starting in 1.21, allowing the simultaneous assignment of both IPv4 and IPv6 addresses. IPv4/IPv6 dual-stack on Kubernetes cluster provides the following features:     Dual-Stack Pod networking(a single IPv4 and IPv6 address assignment per Pod)     IPv4 and IPv6 enabled Services     Pod off-cluster egress routing(eg. the Internet) via both IPv4 and IPv6 interfaces. IPv4/IPv6 Dual-Stack Prerequisites Kubernetes 1.20 or later Provider support for dua...
Read more

What happens under the hood when you create a Java ServerSocket and bind wildcard "0.0.0.0" in a dual-stack host?

Image
Today, I am busy helping a teammate to troubleshoot an issue in Kubernetes cluster. In the investigation, I found it is related to a question that I have been dying to figure out for a long time: what happens under the hood when you create a Java ServerSocket and bind wildcard "0.0.0.0", and this time, it is in a dual-stack host.   For example, in my WSL, it is a dual-stack: And then I run below Java program(just for testing): After I run it in my WSL, I use the netstat command to check the listening socket:  Although I am binding the "0.0.0.0" which is an IPv4 wildcard,  there's a tcp6 LISTENING socket with ":::8888" which is an IPv6 wildcard! So, why? What happens!? Let's delve into it. Firstly, let's check what happens when we create an InetSocketAddress with "0.0.0.0": It will try to resolve the hostname ("0.0.0.0" in our case): InetAddress.getByName(hostname). Let's find what does getAllByName do: private static I...
Read more