desired subdomains are assigned to deployed services #110

Open
opened 2025-02-11 14:26:05 +01:00 by kiara · 1 comment
Owner

As a Fediversity user,
I want to use selected sub-domains for my services,
so that I may configure the URLs to my visitors' needs.

implementation notes

clients / utils
v client / > server hickory acme bind technitium powerdns
octodns
DNS control ?

| godns | | | | | |

given this compatibility matrix, the path of least resistance to automating DNS would seem server bind (optionally with client octodns (thru TF / NixOS-DNS)).

c.f.:

open questions

  • should we integrate with external registrars / DNS providers (e.g. openprovider)?
**As** a Fediversity user, **I want** to use selected sub-domains for my services, **so that** I may configure the URLs to my visitors' needs. ## implementation notes <details> <summary> clients / utils </summary> - clients - [octodns](https://github.com/octodns/octodns) - [wiki](https://wiki.nixos.org/wiki/Octodns) - [providers](https://octodns.readthedocs.io/en/latest/#providers) - [TF](https://registry.terraform.io/providers/topicusonderwijs/octodns/latest/docs) - given an API spec may generate client [for python](https://github.com/openapi-generators/openapi-python-client) - may ([without TF](https://github.com/Janik-Haag/NixOS-DNS/issues/5)) be configured using [NixOS-DNS](https://janik-haag.github.io/NixOS-DNS/) ([source](https://github.com/janik-haag/NixOS-DNS/)) - [DNS control](https://dnscontrol.org/) ([wiki](https://wiki.nixos.org/wiki/Dnscontrol), [providers](https://docs.dnscontrol.org/provider/index)) - ~~[clan dyndns module](https://github.com/clan-lol/clan-core/blob/main/clanServices/dyndns/default.nix)~~: tied to their service - [`godns`]() ([module](https://search.nixos.org/options?channel=unstable&show=services.godns.settings&query=services.godns), [providers](https://github.com/TimothyYe/godns#supported-dns-providers)) - utilities - [`dns.nix`](https://github.com/nix-community/dns.nix): zone files - [nixcloud-webservices](https://github.com/nixcloud/nixcloud-webservices/tree/dns/modules/services/dns): [helpers to generate strings for a few resource records](https://discourse.nixos.org/t/nix-dns-a-nix-dsl-for-dns-zone-files/2466/5) </details> | v client / > server | hickory | acme | bind | technitium | powerdns | |-|-|-|-|-|-| | [octodns](https://octodns.readthedocs.io/en/latest/#providers) | | | ✅ | | ✅ | | [DNS control](https://docs.dnscontrol.org/provider/index) | | | [✅](https://docs.dnscontrol.org/provider/bind) | [?](https://github.com/StackExchange/dnscontrol/pull/3218) | [✅](https://docs.dnscontrol.org/provider/powerdns) | ~~| [`godns`](https://github.com/TimothyYe/godns#supported-dns-providers) | | | | | |~~ given this compatibility matrix, the path of least resistance to automating DNS would seem server `bind` (optionally with client octodns (thru TF / NixOS-DNS)). c.f.: - [selfhostblocks ticket](https://github.com/ibizaman/selfhostblocks/issues/63) ### open questions - should we integrate with external registrars / DNS providers (e.g. [openprovider](https://github.com/openprovider/api-documentation))?
kiara added this to the Fediversity project 2025-04-18 10:21:02 +02:00

This needs to be rewritten to a user story instead of being phrased in terms of implementation details. If I try imagining what it would be like, I don't see the difference to #109. Isn't all of this actually about being able to (register and then) select a DNS record before deployment?

This needs to be rewritten to a user story instead of being phrased in terms of implementation details. If I try imagining what it would be like, I don't see the difference to #109. Isn't all of this actually about being able to (register and then) select a DNS record before deployment?
kiara changed title from The deployment process informs the DNS service of the IP of provisioned VMs, so that the right subdomain can be assigned to it to desired subdomains are assigned to deployed services 2025-04-30 14:33:51 +02:00
kiara removed this from the Fediversity project 2025-06-10 19:07:00 +02:00
kiara added this to the Fediversity project 2025-11-04 19:34:50 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: fediversity/fediversity#110
No description provided.