From d5ee358ef1ec59d550dc7526cf894c3447747387 Mon Sep 17 00:00:00 2001 From: Florian Haas Date: Tue, 13 Jan 2026 15:10:49 +0100 Subject: [PATCH] fix: Update Designate limitations The Limitations section erroneously still claimed that Cleura Cloud doesn't support Designate. Update it to the effect that while we do support Designate, our implementation does not support maintaining DNS PTR records. --- docs/reference/limitations/openstack.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/reference/limitations/openstack.md b/docs/reference/limitations/openstack.md index 75c7073ef..b9e3f4c06 100644 --- a/docs/reference/limitations/openstack.md +++ b/docs/reference/limitations/openstack.md @@ -69,8 +69,9 @@ To expose a service via IPv4 *and* IPv6, you must set up two separate load balan ## Designate -The [OpenStack Designate](https://docs.openstack.org/designate/) DNS-as-a-service (DNSaaS) facility is currently not available in {{brand}}. -You must manage your own DNS records for public IP addresses. +### PTR Records + +The [OpenStack Designate](../../howto/openstack/designate/index.md) DNS-as-a-service (DNSaaS) facility in {{brand}} currently does not support managing [PTR records](https://en.wikipedia.org/wiki/PTR_record). ## Manila