Skip to content
Log inDashboard

Our network

opdns answers from its own addresses, announced from its own autonomous system. Every location (PoP) announces the same prefixes, and routing on the Internet takes each query to the closest one: this is anycast.

What Address
Resolver host name dns.opdns.net
IPv4 23.166.164.53 and 23.166.164.35
IPv6 2602:81f:6000::53 and 2602:81f:6000::35
Each profile’s own IPv6 address one per profile, in 2602:81f:6000::/48

dns.opdns.net points to 23.166.164.53 and 2602:81f:6000::53. The second addresses are for settings that ask for two DNS servers. Which address to use for what is in Your endpoints.

Each server also has an address of its own, used to operate and monitor it. Use the addresses above, not those: a server’s own address answers only queries that name your profile (DNS-over-HTTPS, DNS-over-TLS or DNS-over-QUIC) or come from one of your linked addresses, and refuses everything else.

What Value
Autonomous system AS403104 (AS-OPERO-NETWORKS), registered with ARIN to Solutions Opero Inc, the company that runs opdns
AS-SET AS403104:AS-OPERO
IPv4 prefix 23.166.164.0/24
IPv6 prefix 2602:81f:6000::/48

Both prefixes are signed in RPKI: their route origin authorisations (ROAs) allow only AS403104 to announce them, so networks that check RPKI drop anyone else’s announcement. Both also have route objects with origin AS403104 in ARIN’s routing registry (IRR).

Toronto, Dallas, Atlanta, Chicago, Los Angeles, Seattle and London answer these addresses today, and more locations will join. The status page shows every location and its state, live.

About Write to
Routing, peering and network operations [email protected], Opero’s network desk, also the contact in ARIN’s registry for AS403104 and both prefixes
Abuse involving our addresses [email protected], see Reporting abuse