Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
leon3s opened this issue May 31, 2023 · 0 comments
Open

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

leon3s opened this issue May 31, 2023 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed ncdns Include change in `bin/ncdns` ndns Include change in `bin/ndns`

Comments

@leon3s
Copy link
Member

leon3s commented May 31, 2023

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.
@leon3s leon3s added enhancement New feature or request good first issue Good for newcomers ncdns Include change in `bin/ncdns` ndns Include change in `bin/ndns` labels May 31, 2023
@leon3s leon3s added help wanted Extra attention is needed labels May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed ncdns Include change in `bin/ncdns` ndns Include change in `bin/ndns`
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leon3s