kebrot ricpumanes

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,

	// A common redux pattern when dealing with async functions is to use thunk.
	// This usually means your action returns a new function instead of an action object,
	// and the thunk middleware will make it all work. Example:
	const asyncAction = () => dispatch => setTimeout(() => dispatch(someOtherAction()), 10000);

	// Now: maybe that async stuff going on is calling some API which you don't want to overload
	// with request, and that's what debounce is for.
	// This is an example of a debounced function which will only be calleable once every second.
	import { debounce } from 'lodash';
	const debouncedFn = debounce(() => callApi(), 1000, { leading: true, trailing: false });

	/*
	No jQuery necessary.
	Thanks to Dan's StackOverflow answer for this:
	http://stackoverflow.com/questions/123999/how-to-tell-if-a-dom-element-is-visible-in-the-current-viewport
	*/

	function isElementInViewport(el) {
	var rect = el.getBoundingClientRect();
	return (
	rect.top >= 0 &&