include DNSSEC records in zone export API

Open
#654 0 comments 4 reactions 0 assignees View on GitHub

Maintainers usually reply within 14 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, networking

Research direction

Start by reading the zone export API documentation linked in the issue and trace the corresponding API implementation and tests in desec-stack. Check how DNSSEC records are represented and whether export options are already supported. Done means an optional opt-in export includes DNSSEC records while the existing default behavior remains unchanged.

Written by the indexing model from the issue text.

Description

enhancement help wanted

Currently the API to export a DNS zone does not include DNSSEC records:
https://desec.readthedocs.io/en/latest/dns/domains.html#exporting-a-domain-as-zonefile

it would be great to include all zone records, including DNSSEC related records
as a stop-gap solution until AXFR #579 is implemented.
This could be an optional opt-in parameter.

related to:
https://talk.desec.io/t/zone-transfer-to-secondary-ns-for-availability-reasons/568

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.