We need a DNS server with a history database, not just a cache, preferably with a distributed history database.

Visit a website and it was blocked by the "official" DNS? Declare the IP invalid in the webUI (or the browser plugin) of the local DNS and it will get you the previous IP from the database.

▲

CodeArtisan 3 days ago | parent | next [-]

Brave browser launched a blockchain based domains registry IIRC.

▲

patrickmay 3 days ago | parent | prev | next [-]

Or teach people how to point to a different DNS server in an area with laws more amenable to their preferences.

▲

prmoustache 3 days ago | parent [-]

Until coutry implement the great firewall and it becomes a play of cat & mouse.

▲

M95D 18 hours ago | parent [-]

... or until the blocking starts at the root name servers. There are only a few of them.

	▲	immibis 8 hours ago \| parent [-]
		The root zone file is publicly distributed by IANA [1] so you can download it and ignore the servers themselves. Then your lookup (from the resolver you're running yourself) starts at a particular country's top level. As for censorship, because it's hierarchical, they'd have to remove an entire country code from the root servers. [1] https://www.iana.org/domains/root/files

▲

SoftTalker 3 days ago | parent | prev | next [-]

/etc/hosts, and /etc/resolv.conf.

	▲	M95D 18 hours ago \| parent [-]
		And get the original IP from where?

▲

numpad0 3 days ago | parent | prev [-]

Domain Name System was an app on the Internet. It wasn't something that always existed. The purpose of it is to provide intuitive means to look up IP address from more intuitive domain name strings.

If you could come up with an alternative system to derive the IP address of desired remote host, or content, e.g. Magnet Link standard, you can just skip DNS and switch to that instead.

TLS can be a problem as a lot of moving parts of WWW now depends on DNS. But all of those can be solved.