DNSi is a question box that rides on DNS, the one service every phone, laptop, router and controller on earth can already speak. If a device can look up a domain name, it can ask an AI a question.
Think of directory assistance: you dial a number, say a name, and a person tells you the answer. The internet has had that since 1983. It is called DNS, and until now it only knew one kind of answer: what number is this name?
DNSi teaches it a new trick. The question travels as a domain name, the answer comes back as the reply. No app to install, no account, no website to open.
One command instead of opening a browser. You live in a shell; the answer lands in it.
Hotel wifi, airplanes, locked-down offices. They block apps and websites. DNS is the one lane that stays open.
A printer, a sensor, 20 year old firmware. A plain name lookup returns the answer text, plus a clock, a UUID and a hash.
"How do I connect to the VPN" becomes a name anyone in the office can look up. IT writes it once, everyone asks by typing.
Sandboxed agents that may only resolve DNS get a sanctioned question and tool channel. Rate limited, log-free.
dig, nslookup, Python, C, BusyBox. If it can resolve a name, it is already a DNSi client.
| Where | Who can ask | Good for | Cost |
|---|---|---|---|
| Your machine | only you | personal terminal Q&A, trying it out | free |
| Your LAN | everyone on the network | team knowledge, device fleets | free + AI tokens |
| The internet | anyone, or token holders | public utility, paid service | ~$5/month VPS + AI tokens |
One deployment can serve an open zone and a token-protected zone at the same time. A wrong or missing token is refused.
It is a deliberate repurposing of the internet's oldest question-answering machine, built with the safeguards security teams expect: rate limits, load shedding, zero per-user logging, and an option to answer over TCP only. Questions and answers travel in plain text, so do not send passwords through it.