reproduce DNS VM #200
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#225 kick-started initial feedback cycle
fediversity/fediversity
#1374 fallback available for DNS/email
fediversity/fediversity
#116 hypervisor resources are provisioned to deploy services to
fediversity/fediversity
#309 port infra to terraform
fediversity/fediversity
#833 unit-tested functionality integrated in deployment pipelines
fediversity/fediversity
Reference
fediversity/fediversity#200
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
needed to test #104
implementation notes
powerdnsakapdns(GPL-2.0, C++, stringly module), front-end powerdns-admin - procolix currently has most experience operating thishickory-dns(MIT/Apache, rust, structured module)acme-dns(MIT, go, semi-stringly module)bind(Apache, C, structured module, wiki, offers DNSSec)technitium-dns-server(GPL-3.0, python, simple module)core-dns(stringly? module)tinydns(stringly module)if we may put off related front-ends until #350, we should be able to handle DNS using Nix options such as
NixOS-DNS, including for the purpose of migration (#100).kiara referenced this issue2025-05-01 16:24:14 +02:00
You're looking for an authoritative DNS server, of course. I suggest you look at Knot DNS. It's a modern DNS server developed by the .cz NIC. It can be a (hidden) master or slave, it has modern interfaces and has pleasant dynamics. It is not a caching resolver, that'd be the user end of things.
@vanrein thanks, that may well be of (future) interest.
now, so far i've maybe somewhat tried to distinguish DNS servers for our internal automation use (immediate concern) vs user-facing applications in that area (to be added to #380 - iirc @koen would be quite interested).
for now over here i've tried to focus on the immediate concern still. i will admit i feel biased against many of the options in this space (considering C itself dated), but immediate pragmatic considerations seem to currently point in favor of BIND DNS as offering a the most usable nix module on top of supporting some of the DNS clients we could use for automation (see #110).
eventually tho both such integrations are something we could build for any of the software in this space, so this is definitely to be revisited as we settle on something amenable as an operator-facing application as well.