mix-dns
@nymproject/mix-dns resolves hostnames to IPs through the Nym mixnet. Each lookup is a DNS-over-HTTPS (DoH) request to a public resolver via the IPR (Internet Packet Router) exit gateway, not through the browser or OS resolver.
┌──────────────────────────────────────────────────────────────┐
│ Your browser app │
│ └─ mixDNS('example.com') │
│ └─ mix-tunnel (smolmix-wasm, Web Worker) │
│ └─ DoH request (TCP + TLS) via the IPR │
│ └─ DoH resolver (default Quad9, then │
│ Cloudflare, then Google) │
└──────────────────────────────────────────────────────────────┘The TLS session runs from the WASM client to the resolver, so the IPR forwards only ciphertext. The resolver sees a query from the IPR’s IP, not yours, and the browser’s own resolver path (the OS stub resolver, any local DoH) is bypassed entirely.
When to use it
mix-dns is for cases where you need the resolved IP itself, not a connection that uses it. mix-fetch and mix-websocket already resolve via the mixnet internally; you don’t need to call mixDNS before either.
Direct uses:
- Validate that a hostname resolves to an expected IP range before connecting through any path.
- Build IP-based allow / deny lists for an app that performs the connection itself.
- Probe whether a hostname is reachable from the IPR exit’s perspective without opening a connection.
Pages about mix-dns
- Get started: install and resolve your first hostname.
- Reference & security: configure the resolver, and what it sees.
- TypeDoc reference: generated from the source.
- Browser example : a runnable example app.
Last updated on