I mean, as far as I know, DNS is decentralized. Anyone can host their own DNS server, or change which server their network/device uses. Google’s is just very commonly used because 8.8.8.8 is easy to remember, but there are thousands of others run by entities big and small, and there’s nothing stopping you from running your own (assuming you manage to get a hold of a static IPv4)
This is the correct answer. The only thing I would add is some devices don’t allow changing the DNS IPs and are hard coded to 8.8.8.8 so Google blocking sites via DNS is still an issue. Of course you could intercept these requests, but with DNS over HTTPS becoming more popular, i would imagine that device manufactures will also start to do certificate pinning as well to prevent people from using their own DNS server.
Even remembering IP addresses isn’t a great because services can change IP addresses at any point.
As others have mentioned DNS, by its design, is decentralized…to a point. If you run your own DNS, you can’t be an authority to .com addresses for example. Even that sentence has caveats.
Generally speaking you can run your own DNS that uses root DNS servers. MPAA and others have attempted to get those servers to stop pirate domains from being resolvable but they’ve essentially said “fuck off”.
IMO, that’s going to be the last battleground, at which point pirating will have no choice but to move to tor and/or to I2P.
deleted by creator
https://en.wikipedia.org/wiki/Domain_Name_System
Already is. Run your own.
https://docs.pi-hole.net/guides/dns/unbound/
I mean, as far as I know, DNS is decentralized. Anyone can host their own DNS server, or change which server their network/device uses. Google’s is just very commonly used because 8.8.8.8 is easy to remember, but there are thousands of others run by entities big and small, and there’s nothing stopping you from running your own (assuming you manage to get a hold of a static IPv4)
This is the correct answer. The only thing I would add is some devices don’t allow changing the DNS IPs and are hard coded to 8.8.8.8 so Google blocking sites via DNS is still an issue. Of course you could intercept these requests, but with DNS over HTTPS becoming more popular, i would imagine that device manufactures will also start to do certificate pinning as well to prevent people from using their own DNS server.
deleted by creator
the answer is always money.
The answer is always DRM and monetization. If you didn’t have enough reasons to not buy products with locked down software, here’s even more reasons.
Do I need a static ip if I plan to only use it locally from my home network?
The box on which the dns server runs will need a static internal IP address.
deleted by creator
If you’re only going to use it from within your own LAN, then no, you don’t need a static public address
I’ve been using Google’s Public DNS for quite a while, should I switch to Cloudflare or NextDNS after reading OP’s post ?
deleted by creator
Can also set up ipv6 dns, those always static.
You would think…
Even remembering IP addresses isn’t a great because services can change IP addresses at any point.
As others have mentioned DNS, by its design, is decentralized…to a point. If you run your own DNS, you can’t be an authority to .com addresses for example. Even that sentence has caveats.
Generally speaking you can run your own DNS that uses root DNS servers. MPAA and others have attempted to get those servers to stop pirate domains from being resolvable but they’ve essentially said “fuck off”.
IMO, that’s going to be the last battleground, at which point pirating will have no choice but to move to tor and/or to I2P.
This reminded me of namecoin which is a block chain based DNS.
deleted by creator