<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>opdns changelog</title>
  <id>https://opdns.io/changelog.xml</id>
  <link rel="self" href="https://opdns.io/changelog.xml"/>
  <link rel="alternate" type="text/html" href="https://opdns.io/docs/changelog/"/>
  <updated>2026-11-01T00:00:00Z</updated>
  <author><name>Solutions Opero Inc</name></author>
  <entry>
    <title>2026-11-01 (in development, not released)</title>
    <id>https://opdns.io/docs/changelog/#2026-11-01-in-development-not-released</id>
    <link href="https://opdns.io/docs/changelog/#2026-11-01-in-development-not-released"/>
    <updated>2026-11-01T00:00:00Z</updated>
    <content type="text">Resolver

- Each server's own address (not the shared addresses) now answers only
  queries that name your profile (DNS-over-HTTPS, DNS-over-TLS,
  DNS-over-QUIC) or come from one of your linked addresses, and refuses
  the rest. The shared addresses answer as before. If you set a server's
  own address as your DNS server, use the shared
  addresses instead.</content>
  </entry>
  <entry>
    <title>2026-10-30 (in development, not released)</title>
    <id>https://opdns.io/docs/changelog/#2026-10-30-in-development-not-released</id>
    <link href="https://opdns.io/docs/changelog/#2026-10-30-in-development-not-released"/>
    <updated>2026-10-30T00:00:00Z</updated>
    <content type="text">Resolver

- Security: Unbound, the resolver software on every PoP and in the
  self-hosted node, is now 1.26.2. It fixes three vulnerabilities in 1.26.1
  and earlier: a slowdown from crafted messages
  (CVE-2026-96405),
  a possible cache poisoning
  (CVE-2026-109125)
  and a DNSSEC validation bypass under a configured trust anchor
  (CVE-2026-35501).
  Self-hosted nodes get it with the next node release; update when it is
  out.</content>
  </entry>
  <entry>
    <title>2026-10-29</title>
    <id>https://opdns.io/docs/changelog/#2026-10-29</id>
    <link href="https://opdns.io/docs/changelog/#2026-10-29"/>
    <updated>2026-10-29T00:00:00Z</updated>
    <content type="text">Resolver

- New addresses, on opdns's own network. dns.opdns.net now points
  to 23.166.164.53 and 2602:81f:6000::53, with 23.166.164.35 and
  2602:81f:6000::35 as second addresses for settings that ask for two. All
  of them are announced from opdns's own autonomous system, AS403104. Each
  profile also has its own IPv6 address for plain DNS now, shown on the
  Setup page. If you typed the old IPv4 address into a router, a computer
  or an app, or copied a DNS stamp before today, replace it with the new
  one: the old address stops answering soon.
  (Your endpoints,
  Our network)</content>
  </entry>
  <entry>
    <title>2026-10-15 (in development, not released)</title>
    <id>https://opdns.io/docs/changelog/#2026-10-15-in-development-not-released</id>
    <link href="https://opdns.io/docs/changelog/#2026-10-15-in-development-not-released"/>
    <updated>2026-10-15T00:00:00Z</updated>
    <content type="text">Resolver

- A profile id that does not exist (mistyped or deleted), a DNS-over-TLS
  or DNS-over-QUIC server name that does not encode a well-formed id, and
  an IPv6 address in the profile range that encodes no profile are now
  answered as the public path:
  unfiltered, not logged, and with no error. Before, they were refused.
  A mistyped address therefore fails silently, so
  check each device after setup.
  (When nothing matches)

Dashboard

- DNS stamps: the Setup page shows a stamp (sdns://) for
  DNS-over-HTTPS, DNS-over-TLS and DNS-over-QUIC, with the device name,
  each with a copy button. (DNS stamps)

Policies

- The privacy policy and the
  terms of service are in effect, no longer drafts.</content>
  </entry>
  <entry>
    <title>2026-10-04 (in development, not released)</title>
    <id>https://opdns.io/docs/changelog/#2026-10-04-in-development-not-released</id>
    <link href="https://opdns.io/docs/changelog/#2026-10-04-in-development-not-released"/>
    <updated>2026-10-04T00:00:00Z</updated>
    <content type="text">Filtering

- Schedules in Parental control block the categories and services you
  pick by the clock, in the profile's time zone, including a recreation
  time mode. (Schedules)
- Block affiliate and tracking links, a Privacy switch, off by
  default. (Affiliate &amp; tracking links)
- Web3 names: per profile and off by default, ENS (.eth) names
  open through a gateway. (Web3 names)
- Cache boost sets a minimum TTL on the answers your devices get.
  (Resolution settings)

Dashboard and API

- The Setup page has a guide per platform, filled in with the profile's
  addresses.
- Activity has filters and a CSV export.
  (Activity)
- API tokens have scopes, chosen when you create one; each operation
  needs one scope. (Scopes)</content>
  </entry>
  <entry>
    <title>2026-10-03 (in development, not released)</title>
    <id>https://opdns.io/docs/changelog/#2026-10-03-in-development-not-released</id>
    <link href="https://opdns.io/docs/changelog/#2026-10-03-in-development-not-released"/>
    <updated>2026-10-03T00:00:00Z</updated>
    <content type="text">Privacy made simple

- The Privacy page is one protection slider with five steps, from
  least to most restrictive; new profiles start in the middle. Individual
  blocklists no longer show: a profile set up some other way shows
  Custom with a reset to the nearest step.
  (Privacy blocklists)
- Device telemetry has one switch per manufacturer (Apple, Microsoft,
  Samsung, Amazon, Xiaomi, Huawei, LG, OPPO/Realme, Vivo, Roku, TikTok),
  all off by default and independent of the slider.
- The log storage region shows as a country and its flag.
  (Storage region)

Self-hosted node, policies and credits

- The self-hosted node is in the beta in both modes: enrolled, managed
  from the dashboard, and standalone, with no account, a profile file and
  a local API. (Self-hosted node,
  Standalone mode)
- A security policy page and
  /.well-known/security.txt on opdns.io and app.opdns.io say how to
  report a vulnerability. There is no bug bounty; reporters are credited.
- Attributions credits every third-party list and
  dataset with its licence and a link; the dashboard's Sources and
  licences page links to it.
- New profiles send authoritative servers an anonymised client subnet
  by default (/24 for IPv4, /56 for IPv6); it can be turned off.
  (EDNS Client Subnet)
- The licence names its Licensor, Solutions Opero Inc, and the legal pages
  name Québec, Canada as governing law.
- The privacy policy,
  terms of service,
  acceptable use policy and
  sub-processor list are published on this
  site as drafts; the privacy policy now states the backup retention (query logs leave backups
  at most 120 days after deletion). This changelog has an
  Atom feed.

Command line

- The opdns CLI is a small forwarder for Linux, macOS, Windows and
  routers: it sends every query to opdns over encrypted DNS with your
  profile id and a device name, falls back between transports, and
  handles captive portals and local names. (Command line)

Suspended profiles

- A profile the operators suspend now refuses every query: the
  resolvers and its enrolled self-hosted nodes answer REFUSED with
  Extended DNS Error 15 (Blocked) and profile suspended, followed by the
  operators' explanation when they give one. The dashboard banner shows
  that explanation too, and the API returns it as
  suspendedpublicreason. The operators' internal note is never shown.
  (Suspended profiles)
- API 0.34.0 removes the deprecated listsurl and listssha256 of the
  node profile response and the release, route and at fields of
  client error reports, ahead of their sunset; nothing used them.
  (API changelog)

Self-hosted node

- /metrics is now on by default, behind the page password when one
  is set; page.metrics: false turns it off.
  (Metrics)
- The container image runs as opdns with the ids 10001:10001 and works
  with a read-only root filesystem (--read-only, readonly: true).
  (Upgrade and back up)
- When port 53 is taken, the startup error names the program holding it
  where the node can see it, and says how to free the port.
  (Free port 53)
- Enrolment errors say why a code was refused (expired, already used, or
  not known to the opdns environment the node points at) and what to do.
  (Troubleshooting)
- Standalone list polling is spread by ±10 % and waits at least the
  download endpoint's Retry-After after a 429 or 503.
  (Standalone mode)
- A node a few minutes slow keeps DNSSEC validation on after a new list
  arrives: the clock check allows an hour behind the list's creation time.
  (Clockless boot)</content>
  </entry>
  <entry>
    <title>2026-09-30 (in development, not released)</title>
    <id>https://opdns.io/docs/changelog/#2026-09-30-in-development-not-released</id>
    <link href="https://opdns.io/docs/changelog/#2026-09-30-in-development-not-released"/>
    <updated>2026-09-30T00:00:00Z</updated>
    <content type="text">Resolver and lists

- Am I using opdns? A public page, opdns.io/check, and a
  panel on each profile's Setup page tell whether this device's DNS goes
  through opdns, and with which profile, identification and transport. It
  works by looking up a random name only opdns answers; the lookup is never
  logged or counted. check.opdns.io TXT gives the same facts on the
  command line. (Check it works)
- The PoPs can no longer be used to amplify attacks: UDP answers are at
  most twice the question's size (four times for identified queries) or
  truncated to TCP, responses are rate-limited per client network, ANY
  gets the short RFC 8482 answer, and DNS cookies (RFC 7873) exempt
  verified clients. Under a reflection-style load test, the bytes a PoP
  sent back fell from 13.7 to 0.5 times the bytes it received.
  (Limits)
- Profiles are signed (Ed25519) on their way to the PoPs and to
  self-hosted nodes, which refuse a profile that is unsigned or signed by
  an unknown key and keep the last good one.
  (Lists and profiles on the PoP)
- The list catalogue (GET /v1/lists) names every source of a list, with
  its licence, the credit it requires and when it last changed.
  (Privacy blocklists)
- New list builds go to a few canary PoPs (server locations) first. After
  15 minutes, their block and SERVFAIL rates are compared with the rest
  of the fleet; the build is promoted everywhere or rejected, and a bad
  build can be rolled back fleet-wide.
  (Lists and profiles on the PoP)
- List manifests, latest.json and a new keys.json of trusted keys carry
  detached minisign signatures, and each build records where its sources
  came from.
- Lists can hold exact (=example.com) and children-only
  (.example.com) rules besides suffix rules (list artifact format 2;
  PoPs and nodes still load format 1). A public suffix is never blocked as
  a whole.
- Every build is checked before it is published: a never-block guard list
  removes block rules on names that must keep resolving, and four gates
  (per-list change, memory budget, guard, popular sites newly blocked)
  refuse a suspicious build, which then never reaches a PoP. List ids are
  never reused.
  (Lists and profiles on the PoP)
- Every PoP runs the same pinned Unbound (1.26.1), built from the verified
  source, and keeps a local copy of the root zone (RFC 8806, checked with
  ZONEMD), so cold lookups no longer go to the root servers.
  (Architecture)
- The PoPs forward EDNS Client Subnet, so the profile's ECS mode now
  applies.
  (Settings)
- Tested clients: which command-line DNS clients
  work over which transport; operating systems and browsers are still to
  be tested.

Dashboard and API

- Analytics globes: the Destinations card is now a dot-matrix globe
  shaded by country, like the Where your queries were answered card, and
  both can be zoomed up to 6x (pinch, Ctrl or ⌘ + scroll, the + and −
  buttons, or the +, - and 0 keys) with finer dots as you zoom in;
  point at a country for its count and share.
  (Using the globes)
- List reports: you get an email when the maintainers accept or
  reject your report; they aim to answer within two business days.
  (Report a wrong block or a miss)
- Query limits on logs and analytics: ranges of at most 31 days for
  the shapes that read every row (400 days for hourly totals), a query
  budget and at most four queries at once per organisation, and a cap on
  what one query may read (rangetoolarge, toomanyqueries,
  querytooexpensive). A query without from covers the longest range
  allowed. (Log query limits)
- API 0.5.2 to 0.6.2: the query limits, signed node profiles, list
  sources and attribution in the catalogue with triagedueat on list
  reports, and node token rotation.
  (API changelog)
- Cloud log retention is at most 90 days (it was up to 730). The menu
  offers 1 day, 7 days, 30 days and 3 months; the API accepts 1 to 90.
  Queries logged on your own node are not limited.
  (Retention)
- Passwords are 12 to 128 characters, with no other rule, and a
  strength meter under every new-password field that advises without
  blocking. New passwords are not checked against breached-password lists.
  (Password rules)
- Suspended profiles: a profile the operators suspend keeps answering,
  without filtering or logging, and shows a banner with its settings
  read-only until it is reinstated.
  (Suspended profiles)
- Analytics: a GAFAM card (the share of queries that reached Google,
  Apple, Meta, Amazon or Microsoft, then the big CDNs) and a Where your
  queries were answered card with a globe of the PoPs that answered; the
  destinations map credits its GeoIP data.
  (Where your queries were answered)
- API 0.2.1 to 0.5.1: retention 1 to 90, the password length codes,
  suspended on profiles with 409 profilesuspended, the toppops
  shape and GET /v1/pops.
  (API changelog)
- Report a wrong block or a miss from a query's details in Logs; your
  reports and the maintainers' decision are under Settings → Lists.
  (Report a wrong block or a miss)
- Analytics: the Destinations card has a world map of answer addresses
  by country, where the deployment has a GeoIP database.
  (Destinations globe)
- Settings hides or disables, with the reason, what this deployment
  does not offer (today the block page).
  (Settings that do not apply here)
- Account security (from an ASVS level 2 review of sign-in): emails
  when an authenticator app, a passkey or recovery codes change, and when a
  reused authenticator code is refused; recovery codes are salted one by
  one; a password change, reset or recovery ends older reset and recovery
  links; adding a second factor lifts only that session's restriction;
  passkey and token names refuse control and invisible characters; new
  Activity entries for failed password changes, wrong codes and reused
  codes; a Show button on every password field.
  (Account)
- API 0.2.0: X-Opdns-Api-Version on every response, Deprecation and
  Sunset headers on deprecated fields, GET /v1/capabilities, list
  reports, country and owner on destinations, a topowners shape,
  and browser security headers on every response.
  (API versioning and deprecation)
- Logs: the live tail is a stream (server-sent events), with a fallback
  to polling every 2 seconds; the indicator says which. Every result shows
  where it came from (Cloud or Your node), and relayed results have their
  own states: asking your node, node offline with an automatic retry, node
  timeout. (Logs)
- Query details say why a query was blocked, allowed or rewritten, with
  the reason code, list or rule, and the Extended DNS Error the device
  received. Allowing a name a security list blocked needs an explicit
  confirmation. (Query details)
- Analytics has a Top reasons card, counted over the whole range by
  the log store. (Analytics)
- Logs and Analytics say when a result from your node is partial, and
  why: near its time limit, reconnecting, or busy.
  (Logs)
- Settings disables the node log destinations until a node is enrolled
  and names the node once there is one; log options that do not apply
  while logs are off say so. (Settings)
- Account → Activity shows the account's audit log. (Activity)
- Account recovery with an emailed link and a recovery code, for an
  owner who lost their authenticator app or passkeys.
  (Account recovery)
- Node offline alerts: owners get an email when a self-hosted node has
  been offline for 10 minutes, and when it is back; a preference turns them
  off. (Nodes)
- Password sign-in slows down after failures, and ten failures in an hour
  send the owner an email. Sessions last at most 30 days, end after 7 days
  unused, and renew their token daily.
- Account → Error reports turns off the dashboard's crash reports for a
  browser.
- API: cursor pagination on every list, Idempotency-Key on creating
  POSTs, the live log stream, audit log endpoints, preferences, account
  recovery, DELETE /v1/nodes/self, and enrolment with a profile.
  (Errors and limits)
- API: every log row carries reason, reasoncode, edecode and
  edetext; a topreasons analytics shape; results relayed from a node
  can be marked partial; dashboard error reports
  (POST /v1/client-errors); profile.update audit
  entries record what changed, from and to.
  (Log query results)

Self-hosted

- Local names: the node answers your network's own names under
  home.arpa (from local.hosts and DHCP lease files) and reverse
  lookups of private addresses itself, and names plain-DNS clients in its
  logs after their host name. On by default.
  (Local names)
- Node token rotation: the node replaces its token every 90 days by
  itself, and opdns-node rotate-token does it now; the previous token
  keeps working for 10 minutes.
  (Rotate the node token)
- Profile signing keys: the node verifies every profile the cloud
  sends; the keys are learnt at enrolment (profilekeys.json, backed
  up) or pinned with cloud.profilepublickeys.
  (Profile signing keys)
- IPv6 preference: on a host without IPv6 the node's Unbound uses
  IPv4 only, and prefers IPv4 when the host has no public IPv6 address;
  unbound.ipv6 overrides it.
  (IPv6 for upstream queries)
- One set of link phases (connected, backoff, offline,
  revoked…) on the local page, in opdns-node status, /healthz,
  the metrics and the log.
  (The link's state)
- Enrolling a standalone node shows the profile it will upload and asks
  first (--yes in scripts), then archives it and stops reading
  profilefile. (Enrol a standalone node)
- The node keeps a local copy of the root zone (RFC 8806, ZONEMD
  checked), on by default, as the PoPs do: cold lookups start at the
  top-level domain's servers. dns.rootzone and dns.rootzonesources
  configure it; the status page shows the copy's serial and age.
  (Local root zone)
- A suspended profile resolves unfiltered and unlogged on an enrolled node
  too. (Suspended profiles)
- Open-resolver guard: the node answers only private, CGNAT, ULA,
  link-local and loopback sources unless dns.allowfrom allows more;
  others get REFUSED. The local page and API answer only the same
  networks and reject unknown host names. Nodes with global IPv6 clients
  need their prefix in dns.allowfrom.
  (Network access)
- opdns-node unenrol revokes the node in the cloud as well
  (--local-only skips it).
  (Unenrol)
- Enrolling a standalone node takes its local profile to the dashboard
  when the dashboard profile is untouched (--keep-cloud-profile to leave
  it out). (Enrol a standalone node)
- Standalone nodes have a local API: read and write the profile, read and
  refresh the lists, with a bearer token.
  (Local API)
- Nodes follow list rollbacks: an announced older version is installed;
  an old notice replayed within 30 seconds of a newer one is ignored.
  (List updates and rollbacks)
- opdns-node config check validates a configuration file and prints
  every value with where it came from (default, file, environment, flag);
  config reference prints every key. The file has a format version.
  (Configuration)
- systemctl reload (SIGHUP) applies dns.allowfrom, web.allowfrom,
  web.hosts, web.passwordhash and store.retentiondays without a
  restart. (Reload)
- A standalone node reloads its profilefile within seconds of an edit;
  an invalid edit keeps the last good profile and shows the error.
  (Standalone mode)
- opdns-node backup and restore move a node, enrolled and with its
  logs, to another host; schema upgrades of the log database copy it to
  backups/ first, and a corrupt database is moved aside instead of
  stopping the node. (Upgrade and back up)
- Logging pauses below store.minfreemb of free disk (500 MB) while DNS
  keeps answering. (Low disk space)
- An optional password on the local page (opdns-node hash-password,
  web.passwordhash), and /metrics is now off unless
  page.metrics: true. (Network access)
- Connections to opdns use TLS 1.3 only; cloud.spkipins can pin the
  cloud's keys. (Connections to opdns)
- The node refuses to start while node.json or secrets/ is readable by
  every user.
- A busy node answers dashboard queries it cannot take with a partial
  result instead of an error (link.maxinflightqueries).
  (Logs on your node)
- The container ships the same pinned Unbound as the PoPs.
- Nodes answer the topowners analytics shape and name the company
  behind each destination address, from classification data built into
  the release; the control plane adds destination countries, since nodes
  have no GeoIP data.
  (Analytics from your node)</content>
  </entry>
  <entry>
    <title>2026-09-29 (in development, not released)</title>
    <id>https://opdns.io/docs/changelog/#2026-09-29-in-development-not-released</id>
    <link href="https://opdns.io/docs/changelog/#2026-09-29-in-development-not-released"/>
    <updated>2026-09-29T00:00:00Z</updated>
    <content type="text">Resolver

- Domain logging off is now applied on the PoP: the name, the answer
  addresses and rule text never leave the machine. Before, they were
  removed later, at ingest.
- Profiles with query logs off now get hourly counts of their queries, so
  Analytics totals and the timeline work with logs off.
- A DNS-over-TLS or DNS-over-QUIC server name that asks for a profile but
  is malformed (a typo in the id, a missing hyphen) is now refused with an
  error instead of being answered unfiltered. (Reversed on 2026-10-15:
  such names are answered unfiltered again.)
- EDNS Client Subnet has three modes per profile: off (the default),
  anonymised (/24 and /56) and full (your address). Forwarding is not yet
  switched on at the PoPs, so for now every mode behaves as off.
- Operator blocks carry a reason code (legalorder, abuse or csam)
  and a public reference in the error text, and always answer NXDOMAIN.
  Queries blocked by a CSAM entry are never logged.
- Operators can block abusive client addresses fleet-wide or per PoP or
  country, for a limited time.

Dashboard and API

- Devices: the devices seen on a profile, with rename, kind, notes and
  forget. Display names show in Logs and Analytics.
  (Devices)
- Parental control uses a real catalogue: 13 categories and 46
  services, each service with a note on what else stops working, each
  category with its sources and their licences.
  (Parental control)
- Setup downloads an iOS and macOS configuration profile, for
  DNS-over-HTTPS or DNS-over-TLS, with the device name filled in. It is not
  signed yet. (iOS)
- Account: export all your data as a zip, and delete your account with
  a 7-day period in which you can change your mind.
  (Account)
- Settings has a choice of EDNS Client Subnet mode.
  (Settings)

Self-hosted

- Nodes learn the list signing key from the cloud (or from the public
  latest.json in standalone mode) and keep it for offline restarts, so
  no key has to be configured.
- A node that is not set up no longer resolves unfiltered: it prints how to
  enrol and exits.
- A hardened systemd unit, with install steps.
  (Install on Linux with systemd)
- Renewed TLS certificates are picked up without a restart;
  systemctl reload forces a reload.
- opdns-node unenrol also forgets the list keys learnt from the cloud.

Lists

- Parental categories and services are curated and reviewed by opdns,
  and compiled into the signed list file the PoPs and nodes load. Sources whose licence is under review are used by
  the cloud only; self-hosted nodes do not receive them.

Policies

- Privacy policy addendum on EDNS Client Subnet, and a status note:
  domain logging off on the PoP and counters for logs-off profiles now match
  what the policy states.</content>
  </entry>
</feed>
