nslord: upgrade PowerDNS Authoritative from 4.8 (EOL since 5.1.0)
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
- Needs clarification
- Activity status
- Active
- Tech stack
- docker, ubuntu
- Domain
- infrastructure
Research direction
Start with nslord/Dockerfile and inspect the PowerDNS repository and version pin; compare it with the 20260525_nsmaster_knot branch, where nslord still uses 4.8. The issue asks whether to upgrade to 4.9 or 5.x or move nslord to Knot, but does not specify which direction is intended. Done means the maintainers choose a supported-software path and nslord no longer runs EOL PowerDNS 4.8.
Written by the indexing model from the issue text.
Description
nslord/Dockerfile still installs PowerDNS Authoritative from the jammy-auth-48 repo, on ubuntu:jammy. Under PowerDNS's EOL policy, 4.8 stopped getting fixes when 5.1.0 was released on 2026-06-03 (announcement, EOL policy).
The 20260525_nsmaster_knot branch replaces nsmaster (and the PostgreSQL 13 dbmaster) with Knot, but nslord on that branch still pins 4.8 as well. nslord isn't publicly reachable, so this is about staying on supported software, not about a known vulnerability.
Is a move to 4.9 or 5.x planned for nslord, or is nslord going to Knot too? Happy to help test if useful.
- 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 ·