>>5343014
As long as you put these into your hosts.txt file and save it, you'll be good in the event of some DNS skull-duggery going down.
104.18.105.234 8ch.net
104.27.141.105 qanon.pub
85.13.154.136 qresear.ch
The instructions in the notables are good, but I believe the hosts.txt file usually has the 'read-only' attribute set, which will need to be disabled fist, in order to allow saving of changes/additions to the hosts.txt file.
This can be done, by right-clicking the hosts.txt file and selecting its properties - look for a 'Read only' checkbox, to untick.
HOSTS.txt and how it works is really very simple, and I probably should have used a bit less tech parlance.
As per the image in my previous post, HOSTS.txt is a relic - it was the precursor to the DNS system we have today.
DNS (Domain Name System) translates human readable domain names (like 8ch.net, for example) to computer readable addresses (The IP version 4 address is 104.18.105.234 - I won't get into IP version 6…).
To access the internet and trhe services hosted at any organisations domain, most people's computers and routers are configured to look out to either their ISP's DNS server, or a public DNS server (less common) to find the latest IP address for a given domain. This is because they can change - your website, for instance, might have been migrated to another web-host and you need the world of potential clients on the 'net to know this - DNS updates achieve that.
DNS servers talk to one another, and they're all being updated from a centrally controlled source or master for the internets DNS records (this process is usually referred to as 'propogation').
If there was fuckery at the DNS root level, it would propogate out quickly and effectively poison the ability of all client devices (ie; your PC, phone, tablet, etc) to resolve domains names to IP addresses correctly - you'd be cut off.
Using the relic that is HOSTS.txt, you bypass internet held DNS records.
Your device looks to the HOST file first to resolve the domain for any request from your device.
If there is an entry for 8ch.net with an IP against it in your hosts file, then your device doesn't even bother looking to an outside DNS server to resolve the record - you've immunised yourself against propogation of bad DNS records from outside of your local network (the infrastructure behind your router).