Sabyasachi Karmakar saby22

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,

Why Multiple SSH keys?

There are numerous reasons you may need to use multiple SSH keys for accessing GitHub and BitBucket

You may use the same computer for work and personal development and need to separate your work.

When acting as a consultant, it is common to have multiple GitHub and/or BitBucket accounts depending on which client you may be working for.

You may have different projects you're working on where you would like to segregate your access.

CREATE

Clone an existing repository

$ git clone ssh://[email protected]/repo.git

Create a new local repository

$ git init

LOCAL CHANGES

Branching

Quick Legend

Description, Instructions, Notes

Instance	Branch

	{
	"states": [
	{
	"id": "1",
	"type": "Union Territory",
	"capital": "Port Blair",
	"code": "AN",
	"name": "Andaman and Nicobar Islands",
	"districts": [
	{


	{
	"AN":"Andaman and Nicobar Islands",
	"AP":"Andhra Pradesh",
	"AR":"Arunachal Pradesh",
	"AS":"Assam",
	"BR":"Bihar",
	"CG":"Chandigarh",
	"CH":"Chhattisgarh",
	"DN":"Dadra and Nagar Haveli",