From 59aef3e8022b59d8388b6d12f40f7f82d32e55a9 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Nov 2026 16:09:41 +0000 Subject: [PATCH 1/2] docs: draft changelog entries for November 11-12, 2026 --- changelog.mdx | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/changelog.mdx b/changelog.mdx index 9ee9f5b..b179ad7 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -6,6 +6,32 @@ rss: true Each entry links to the original announcement in our [changelog discussions](https://github.com/orgs/datum-cloud/discussions/categories/changelog), where you can ask questions and leave feedback. To see what is coming next, read the [roadmap](/platform/roadmap). + + ## Pick the right private zone with `--vpc` + + The `datumctl dns` plugin no longer guesses when several zones share a domain, so a record can't land in another VPC's zone. + + - **Ambiguous zones are refused:** every VPC's default private zone is `datum.internal`. When more than one zone matches the domain you typed, the command stops and lists each zone's object name and the VPCs that use it. + - **New `--vpc ` flag:** uses the zone that VPC resolves. It works on every `record` command and on `zone describe`, `delete`, `nameservers`, `import`, and `export`, for private zones only. + - **Name a zone directly:** pass a zone's object name in place of the domain, for example `datumctl dns record list managed-3f9c2a`. + - Deleting a private zone asks you to confirm with its object name. + - Projects where each domain has only one zone see no change. + + See [Private DNS](/domain-dns/private-dns). + + + + ## Keyboard access and plain permission messages + + The [Cloud Portal](https://cloud.datum.net) is easier to use from the keyboard and explains permission errors in plain language. + + - **Keyboard access:** clickable table rows open with Enter or Space, and the copy badge copies with Enter or Space. + - **Plain permission errors:** raw access-control text is replaced with "You don't have permission to do this." Messages about quota or suspension keep their own wording. + - **Restricted pages** say "An organization owner or admin can give you access." + - **Labelled buttons:** a secret's edit and delete buttons are named for screen readers after the key they act on. + - A DNS zone's settings show DNSSEC as off, with the note "DNSSEC is not available for DNS zones yet." + + ## New load balancers serve traffic sooner From 34c4599186e4c204735a740dd2852833486b460b Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Nov 2026 16:20:48 +0000 Subject: [PATCH 2/2] docs: add Private DNS reliability and proxy readiness changelog entries --- changelog.mdx | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/changelog.mdx b/changelog.mdx index b179ad7..18c6c93 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -20,6 +20,33 @@ Each entry links to the original announcement in our [changelog discussions](htt See [Private DNS](/domain-dns/private-dns). + + ## Private DNS is faster and more reliable + + Instances can look up names in their own VPC through a private zone, and answers stay current as instances come and go. + + - **Answers follow your instances:** when an instance is deleted, its old answers disappear within 1 to 2 seconds. A replacement's new address answers about 4 seconds after the instance is ready. Answers are cached for 30 seconds. + - **First lookup answers right away:** new instances get an answer to their first lookup immediately. Before, DNS gave no answer for 0 to 11 seconds after a deploy or restart, and apps that looked up a name at startup failed with `Temporary failure in name resolution`. + - **No failed lookups during rollouts:** DNS stays up through platform restarts, software updates and edge reboots, because servers drain traffic before they stop. Before, a single rollout caused about 75 seconds of failed lookups. Staging rollouts with steady lookups now lose none. + - **Several servers per resolver address:** several healthy DNS servers share one resolver address, with health checks, in all three regions. A lost host or edge affects only the instances on that host. Requests to a server on another host now get replies instead of timing out. + - **Status you can trust:** zone status shows within seconds whether your records are being served. + - **Isolation between VPCs:** each VPC's answers are isolated from every other VPC. Removing a zone from a VPC returns `NXDOMAIN`, and deleting a VPC withdraws its access from every DNS server. Only the platform can change which DNS a VPC uses. + + Private DNS is in preview. See [Private DNS](/domain-dns/private-dns). + + + + ## New proxies answer within seconds + + A new proxy now answers its first request within seconds in every region, including when its workload runs in a different region than the edge. + + - **Before:** a cross-region proxy returned `503` for about 2 minutes 48 seconds, and sometimes until an unrelated change rebuilt the edge. + - **Now:** in production, a new cross-region proxy answered in 17.5 seconds with no `503` responses, and 30 follow-up requests all succeeded. + - **Network settings reach every instance:** every instance reliably sees changes to VPC network settings, including after a platform restart. + + See [ALB troubleshooting](/alb/troubleshooting). + + ## Keyboard access and plain permission messages