Hacker News Reader

Comment by Xelbair | Hacker News Reader

DNS still runs strong and it was ~~designed~~ released* in the November 1983.

It still holds up basically whole of internet.

in most cases SQL is good enough for 90% of workloads.

Isn't DNS a catastrophic clusterfuck which also had to be patched up multiple times to not allow people burning down the whole world? I mean, yes, it's doing its job, but mainly because of people doing their job.

People who are malicious or see an opportunity for gain will always abuse a system. Just because the DNS system has had to be patched to handle the abuse doesn't mean its badly designed. If it were as badly designed as your comment seems to imply it wouldn't be able to operate even half as well as it does.

The combustion engine's fundamental design is pretty damn good and that it had to be updated to handle unleaded gasoline isn't a knock (pun... intended?) against that design.

Quite the opposite: as it designed in a way that it could be patched and extended, while also being performant.

What would DNS look like if it were released in 2025?

It would be completely centralized with a micropayment rent seeking solution to update records.

I think it would actually be (pseudo-)decentralized and you'd have to mine a blockchain node containing each domain, where its creators will have reserved at least 10% of its node pool to make sure they became billionaires if it took off.

Plus micropayments, of course :-)

Nono, it would run decentralized in blockchain with a mircropayment rent seeking solution to update records.

You’re right that it would run on a block chain, but that fact would primarily exist to power some marketing. Everybody would end up interacting with it through a single centralized web site and API because it’s the only usable way to get it to work.

{txid:"7abde7838e8db8ba98bf8b74be77a9e787be7b8bfb7b893", gas: 0.00015, query: "A", domain: "blabla.com", actual-dns-that-will-resolve-the-query: "8.8.8.8"}

I laughed at first, then I cried, because sadly, it's true.

Owned by GoogleFlare with public spec, but most of it would be run as closed source application that uses extended spec akin to EEE - making it impossible to use without relying on GoogleFlare.

config defined in YAML.

>config defined in YAML.

when I woke up today, I didn't really expect to be convinced that we live in a relatively good timeline, but...

Is there a standard config format for dns currently?

Certainly a JSON-based REST API that is not really RESTful just so that people can complain about it

JSON-Messages over WebSockets. And proper path-format.

Obfuscated behind QUIC.

Certainly some AI features

And it would make it really painful.

But we couldn't get rid of it because it papered over something important.

...and what should it look like?

Ill try answer it myself with more questions. If ranking search results is such a hard problem perhaps dividing domain names should be a tad more complex than giving all the words to the first person to ask as long as they have the money. Perhaps A web directory of some kind but that still doesn't answer the riddle of ordering.

Reply on news.ycombinator.com