you are viewing a single comment's thread
view the rest of the comments
[–] 23 points 1 day ago (7 children)
  • [–] 13 points 1 day ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 day ago

    This is so fucked up and evil that I can only conclude that you've been at Microsoft's mercy before or you are actually a Microsoft employee who is currently bored because your 5 PMs can't breathe down your neck as your company has ground to a halt

  • source
  • parent
  • [–] 1 point 1 day ago* (last edited 1 day ago) (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment