App doesn't take use of the Desired DNS API from the server. #265
Labels
No Label
Blocked
Bug
Contributions welcome
Did not do
Errata
Feature request
Fixed
How To
Invalid
Needs design
No resolution
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Providers
Digital Ocean
Providers
Hetzner
Refactor
Severity
High
Severity
Low
Severity
Medium
Source
Community
Source
Core Team
Source
Stakeholders
Translations
Under investigation
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Blocks
#67 Generate CAA records and add them to the list of required DNS records
SelfPrivacy/selfprivacy-rest-api
#390 Check if we lose control over the domain
SelfPrivacy/selfprivacy.org.app
Reference: SelfPrivacy/selfprivacy.org.app#265
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Right now to determine the desired DNS records we use the hardcoded list, which is duplicated across every DNS provider, and while we do ask the server for the list of desired DNS records, we do this only to get the contents of the DKIM records.
Instead, we must use the data provided by the server. The data it provides is grouped by services which request the corresponding DNS record.
As you can see, we can get the DNS records of the service, and we can get the full list of the DNS records. But:
All these problems can be fixed on the API side.
Related issue 216.
Blocked until resolution on API end.