fix: Update Designate limitations #447
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
fghaas
force-pushed
the
update-designate-limitations
branch
from
378af9d to
d5ee358
Compare
colder-is-better
approved these changes
Jan 13, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.