next-hat/nanocl

Change: Currently the ncddns use dnsmasq, we should move to knot

Open

#354 opened on May 31, 2023

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Rust (51 forks)auto 404
enhancementgood first issuehelp wantedncdnsndns

Repository metrics

Stars
 (983 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. Dnsmasq cannot bind on a new interface without have to fully restart, this will create downtime. I think a fit for our usecase is to use knot dns instead.

Contributor guide

Research direction
Study the current dnsmasq configuration in the ncddns module, then learn how to configure knot DNS as a replacement, focusing on dynamic interface binding without restart.
Tech stack
rust
Domain
backendnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustDNS fundamentals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75