Jesper Eneberg jespereneberg

Permanent WSL DNS Fix (WSL 2.2.1+)

If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.

This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.

DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.

To upgrade WSL, follow these steps,

	Install WireGuard via whatever package manager you use. For me, I use apt.

	$ sudo add-apt-repository ppa:wireguard/wireguard
	$ sudo apt-get update
	$ sudo apt-get install wireguard

	MacOS
	$ brew install wireguard-tools

	Generate key your key pairs. The key pairs are just that, key pairs. They can be

	[Unit]
	Description=Description of this service

	[Service]
	Type=simple
	ExecStart=/usr/bin/nohup /path/to/server.sh
	Restart=always
	RestartSec=30
	StandardOutput=/path/to/log
	StandardError=/path/to/log

	##################################################
	### Elasticsearch host name
	ES_HOST = "search-******************.ap-northeast-1.es.amazonaws.com"

	### Elasticsearch prefix for index name
	INDEX_PREFIX = "awslogs"

	#################################################
	### ELB access log format keys
	ELB_KEYS = ["timestamp", "elb", "client_ip", "client_port", "backend_ip", "backend_port", "request_processing_time", "backend_processing_time", "response_processing_time", "elb_status_code", "backend_status_code", "received_bytes", "sent_bytes", "request_method", "request_url", "request_version", "user_agent"]

	import boto3
	print(boto3.client('sts').get_caller_identity()['Account'])