Network & DNS
Where your traffic leaves from, and what answers a name lookup before the answer reaches the agent that asked.
In this chapter
- Egress5 pagesPut an agent's outbound connections behind its own address, and let the far end confirm which one it saw.
- Resolver3 pagesName lookups checked against the graph before they are answered, and the account policy that decides the rest.
- Devices1 pageWhat a phone or a laptop gets from your account when it resolves names through Whisper and runs nothing else.
- Authoritative DNSWhich zones Whisper answers for, what signs them, and how a name under your own apex joins them.
Network & DNS Documentation
A Whisper identity is a routable address, so it has a place of its own on the wire. This chapter covers what that address sends and what answers for it.
whisper run curl -s https://rdap.whisper.online/egress-ip
{"ip":"2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478"}
That echo needs no key, and the address it reports is the one the far end saw. Egress is where you set that up: a routed tunnel, a bound proxy, or an HTTPS relay for a runtime that holds no sockets.
The resolver is the other half. Every name your agents look up is checked against the Whisper graph before it is answered, and your account decides what happens to the names the graph has no opinion about. A phone or a laptop can sit behind the same resolver without running an agent at all, which is what Devices is for.
Underneath both sits the signed zone work: the forward and reverse records that make an address checkable by a stranger, and the apex you can delegate to put identities under your own name. That is Authoritative DNS.
If you have not minted an identity yet, start at Create an Identity; the address it hands back is what every page in this chapter operates on.