Stale zone served (including DNSKEY) after zone deletion/recreation
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
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.tldmeanwhile 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from desec-io/desec-stack
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
desec-io/desec-stack#1312 ·
Maintainers usually reply within 14 days
-
UI bug and inconsistency: Adding IPv6 address/netmask to token IP restriction silently errors outOpen
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
desec-io/desec-stack#1310 ·
Maintainers usually reply within 14 days
-
Here-strings in request examplesPossibly taken @jadhavgaurav claimed this 28 days ago. Opendocs help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
desec-io/desec-stack#1286 · 1 comment ·
Maintainers usually reply within 14 days
-
api enhancement prio: low
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
desec-io/desec-stack#1246 · 1 comment ·
Maintainers usually reply within 14 days
-
enhancement gui help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
desec-io/desec-stack#1181 · 1 comment ·
Maintainers usually reply within 14 days
All issues in desec-io/desec-stack
Similar issues
-
[dbt] exported dataset keys reference physical columnsPossibly taken @WilliamKelley claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/ossie-converters#251 ·
Maintainers usually reply within 2 days
-
cli difficulty: easy enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws/aws-durable-execution-sdk-python#977 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
flashinfer-ai/flashinfer#9803 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
iamprivacy/Waves#66 · 2 comments ·