Identification
Every query is matched to a profile, and optionally a device, from the transport it arrived on. A transport only ever uses its own source; there is no guessing across them.
| Transport | Profile from | Device from |
|---|---|---|
| DoH, DoH3 | first path segment: https://dns.opdns.net/abc123 |
second segment: /abc123/Living-Room-TV |
| DoT, DoQ | TLS server name: abc123.dns.opdns.net |
prefix before the last hyphen: living-room-tv-abc123.dns.opdns.net |
| Plain DNS over IPv6 | the destination address: the profile id is encoded in the address | none |
| Plain DNS over IPv4 | the source address, if it is a linked IP | none |
Profile ids are case-insensitive: 6 characters, a-z and 0-9, never
000000. Device names are sanitised (letters lowercased, spaces, dots and
underscores to hyphens, other characters dropped, 32 characters max). The
device id is derived from the profile and the name, so the same name on
any PoP (opdns server location) or node is the same device.
The IPv6 encoding
Section titled “The IPv6 encoding”Each anycast IPv6 prefix is a /48. Inside it, an address of type 1 carries the profile id as a base-36 number in its low 32 bits (the 6-character id fits in about 31 bits):
<48-bit prefix> : 0 : 0 : <type> : <id as base 36, 32 bits>2001:db8:1::1:252c:e35b type 1: profile abc123 in 2001:db8:1::/482001:db8:1::53 type 0: the service address (public path)opdns’s profile prefix is 2602:81f:6000::/48, and its service addresses
are 2602:81f:6000::53 and 2602:81f:6000::35. The encoding is frozen; an address
you configure will keep working.
Type 0 is the public path’s service address; an address of another type,
or one that encodes a profile that does not exist, is answered as the
public path too (see below).
When nothing matches
Section titled “When nothing matches”| Case | Result |
|---|---|
Plain DNS from an unlinked address, DoH to / or /dns-query, DoT/DoQ to dns.opdns.net itself or with no server name |
the public path: unfiltered, not logged, rate-limited |
| A well-formed id that is not a profile, or no longer is (any transport) | the public path, exactly as if the query named no profile; no error says the id is unknown |
A DoT/DoQ server name under dns.opdns.net that does not encode a well-formed id (wrong length or characters, a device name joined without its hyphen, a deeper name) |
the public path |
A DoT/DoQ server name outside dns.opdns.net |
the public path |
| An address in the profile IPv6 range whose type is reserved | the public path |
| A DoH path that is not an id | HTTP 404 |
A source that asks for a profile and gets it wrong is not refused: it is answered like any query without a profile, unfiltered and not logged, under the public path’s rate limits. So a typo fails silently: the device keeps resolving, without your filtering. After any setup, check it works: a mistyped id shows as Not filtered.
A self-hosted node differs in one way: queries that identify no profile, including the cases above, get the node’s own profile (it serves one profile to the whole network), so they are filtered by it.
Why plain IPv4 cannot name devices
Section titled “Why plain IPv4 cannot name devices”A plain DNS query carries the question and nothing else. On IPv6, the profile’s own addresses tell the resolver which profile was meant; on IPv4 the addresses are shared, so the only signal left is who is asking. opdns has declined to guess devices from addresses (the comparison lists this); encrypted DNS is the way to name devices.