Stale zone served (including DNSKEY) after zone deletion/recreation

Open
#1,229 1 comment 0 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
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
networking

Research direction

Start by comparing the DNSKEY shown in the domain setup instructions with the records returned by both authoritative nameservers after deleting and recreating the domain. Read the domain deletion/recreation and DNSSEC key-serving paths; the issue does not name specific files or tests. Done means the instructions and authoritative DNSKEY agree after recreation, or the mismatch has a documented cause.

Written by the indexing model from the issue text.

Description

api bug

I'm experiencing an issue with my domain managed on deSEC and I'm unsure whether it's me who messed up her DNSSEC or maybe a bug in the platform. I beg for pardon if it's just me who's overwhelmed with DNSSEC.

I have a domain registered on deSEC. I accidentally deleted it and re-added it importing a previous zonefile. Of course, the DNSSEC setup at my registrar had to be adjusted afterwards so I published the new DS records to my domain.

After waiting for the TTL to pass twice, I checked the configuration again and found some oddity :

The setup instructions of my domain show me a DNSKEY Format with another public key than when I query the DNSKEY record at the two authoritative nameservers.

  • The setup instructions show me a record as follows : 257 3 13 ObslXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXJazQ==
  • dig @2607:f740:e633:deec::2 DNSKEY mydomain.tld meanwhile reports the following : 257 3 13 gmCLXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXMOTw==

(Number of X just estimated.)

I'm now unsure whether I maybe messed up even more or whether deleting and re-adding the domain might have broken something in your stack ?

I temporarily disabled DNSSEC by removing the DS record at my registrar in case this might help.

I'm really looking forwards to find a solution to this oddity.

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.