New Issue

App doesn't take use of the Desired DNS API from the server. #265

Open

opened by inex · 2 comments

inex commented

Owner

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:

The full list does not include the link to the service (probably we can make one)
API does not advertise itself as a service yet, so you can only get its record from the full list?
No root records are provided

All these problems can be fixed on the API side.

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. ![image](/attachments/ebb96337-2b90-4fde-8383-0426468113c5) 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: - The full list does not include the link to the service (probably we can make one) - API does not advertise itself as a service yet, so you can only get its record from the full list? - No root records are provided All these problems can be fixed on the API side.

image.png

184 KiB

inex added the

Feature request

Refactor

labels

inex referenced this issue from SelfPrivacy/selfprivacy-rest-api

Root record is not provided by the Desired DNS API #47

inex referenced this issue from SelfPrivacy/selfprivacy-rest-api

[GraphQL graph] DNS Record endpoint should link to the service #48