In order to solve this problem, we’ve replaced DNS with AI. What was previously a DNS server is now a webserver that runs a GraphQL endpoint that has one query and that one query has one parameter called “prompt”. It accepts prompts, which are strings of the form “Chat, what IP Address should I connect to if I wanted to talk to facebook.com”
For security you can also ask it “Chat, what IP Address should I connect to if I wanted to talk to facebook.com, and what public key should I use”
It should be highly accurate, because it was trained on a scraped copy of all the domain names we could find in March of 2024. You pay us for it in tokens.
tropicaldingdong@lemmy.world@lemmy.world
FridaVanMercury@discuss.tchncs.de
ScoffingLizard@lemmy.dbzer0.com 8 hours ago
I made a post in the privacy community about a bad DNS leak for NextDNS users. Got a few servers ordered days ago for redundant DNS self hosting. Planning on two Pi holes with Unbound.
How do you think it was a DNS hack? I’ve been thinking the two issues were not coincidentally within days of each other, but maybe I’m wrong.