3 ms·
I agree with Paul Vixie. The internet, IMO, is not a playground for large corporations. What originally made the Internet amazing was the participatory nature
by vkaku 8y ago
I agree with Paul Vixie. The internet, IMO, is not a playground for large corporations.
What originally made the Internet amazing was the participatory nature of it. As it started 'standardizing' or 'accruing', autonomy was lost in the pursuit of efficiency.
Today, 2-3 corporations are just trying to own the internet, and this needs to stop. I favour a participation in the Internet than what it is today.
Okay, so how can we make it happen?
- Make a decent DNS Server in Go/Rust/<Any-Clean-Coded-Implementation>.
- Make this embeddable in routers/open stacks, maybe in OpenWRT.
- Make it easier to define top level zones/domains in a modern, easy data format (maybe JSON/YAML). Make this an overlay/augment format.
- Publish bootstrap corpus of data for such independent DNS servers; No, they do not need to have all the root server content updated as frequently. It could be easy to sync this periodically with a git pull. This should be an internet-wide mirrored effort, like Bitcoin.
- Isolate oneself from people, arguments and organizations who want to use AWS/Google/<Insert-Popular-Provider-Of-Choice> because they work at scale and are cheap. One should know that to have an independent internet, the change starts with the self.
- Run the DNS server at home, production, *cloud and protect the Internet.
- leowoo91 8y agoCongratulations, you've just spend your time, and your mobility.
- xorcist 8y agoWhat's wrong with opkg install unbound? It's robust, doesn't require maintenance, and already available an an optional install in OpenWRT. The reason people don't use it is probably just that it isn't default. Some captive portals mess with DNS resolution and it's probably easier for OpenWRT to just let them.
- lazyjones 8y ago> What's wrong with opkg install unbound? It's robust, doesn't require maintenance, Good joke. It's written in C, so in addition to typical protocol/logic flaws, it'll have its share of security and memory leak problems. No maintenance? Have a look at https://nlnetlabs.nl/svn/unbound/tags/release-1.9.1/doc/Changelog https://nlnetlabs.nl/svn/unbound/tags/release-1.9.1/doc/Chan... and its security advisories... Regular updates are necessary.
- upofadown 8y agoHere is a list (and some discussion) of the 4 CVEs that unbound has had starting in 2011: * https://nlnetlabs.nl/projects/unbound/security-advisories/ https://nlnetlabs.nl/projects/unbound/security-advisories/ Nothing there looks particularly scary to me.