API: Query for DNS record propagation

Open
#577 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 14 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

No files, tests, or API entry points are named; start by reading the existing API documentation and how it represents RRSet changes. First clarify what propagation status should mean across authoritative anycast servers, including removals; done would require an agreed response or pending-changes design and tests for its behavior.

Written by the indexing model from the issue text.

Description

api enhancement

For some applications (ACME challenges, TLSA records, ...), it is interesting to know, if a record that was just added/updated/removed/... has fully propagated to the authoritative nameservers. Just querying the authoritative nameservers is not sufficient, due to the anycast network. Some frontend servers may already have the data, others may not, but I can only query those, that are closest to me.

Particularly when the network is slow to update, it would be useful to have some way to find out if all servers have/publish the same information. Since I do not believe this can be done in DNS, I suggest adding it to the API.

I don't have a clear idea, of how this should look like.
It could be an additional JSON field that is returned for all RRSets. I'm not sure how to indicate the propagation status of record removal.
Another option might be to provide a list of pending changes.

Dominant language
Python
Stars
678
Forks
74
Avg merge
7d 23h
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from desec-io/desec-stack

All issues in desec-io/desec-stack

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.