fediversity/fediversity

Watch

Fork 10

desired subdomains are assigned to deployed services #110

New issue

Open

opened 2025-02-11 14:26:05 +01:00 by kiara · 2 comments

kiara commented

2025-02-11 14:26:05 +01:00

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

clients
- octodns
  - wiki
  - providers
  - TF
  - given an API spec may generate client for python
  - may (without TF) be configured using NixOS-DNS (source)
- DNS control (wiki, providers)
- ~~clan dyndns module~~: tied to their service
- godns (module, providers)
utilities
- dns.nix: zone files
- nixcloud-webservices: helpers to generate strings for a few resource records

v client / > server	bind	powerdns	eon	knot	deSEC	commercial DNS providers
octodns	✅	✅		❌	✅	many
DNS control	✅	✅				many
eilean (example)	✅		✅			❌ none

~~| godns | | | | | |~~

judgement: given this compatibility matrix, the path of least resistance to automating DNS would seem server bind (optionally with client octodns (thru TF / NixOS-DNS)) or (given a nix package/module, possibly thru ngipkgs) deSEC.
as an alternative to interfacing with upstream DNS providers, we could initially presume hosting providers would have registrar status (pilot with ProcoliX: EURid registrar), significantly reducing the number of potential upstreams to interface with.
- ~~EURid has a €2500 signup fee, lacks public API documentation, and ProcoliX isn't a registrar with them so far, tho EURid's interface is like EPP~~
metaregistrar (dutch commercial entity, TF DNS challenge 1 2) was suggested by procolix as a registrar that serves many registries, for short-term demo purposes (with long-term intent to instead do an open-source registrar connecting many registries). (for what it's worth, this registrar appears not currently suggested by any of our listed DNS clients.) - seems not as convenient so far as the automation already available for the below
opusdns (DE, not for individual consumers) offers a TF provider for domain registration, while for DNS seeming covered by octodns. as such, this might make for one easy way for us to get going in an automation-friendly manner.

c.f.:

selfhostblocks ticket

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 | [eon](https://ryan.freumh.org/eon.html) | knot | deSEC | commercial DNS providers | |-|-|-|-|-|-|-|-|-|-| | **[octodns](https://octodns.readthedocs.io/en/latest/#providers)** | | | ✅ | | ✅ | | ❌ | ✅ | many | | [DNS control](https://docs.dnscontrol.org/provider/index) | | | [✅](https://docs.dnscontrol.org/provider/bind) | | [✅](https://docs.dnscontrol.org/provider/powerdns) | | | | many | | [eilean](https://github.com/RyanGibb/eilean-nix/tree/main/modules/services/dns) ([example](https://github.com/RyanGibb/eilean-nix/blob/38d1e94d7307d41ad0fbce0cf719af581d4c8696/modules/mailserver.nix#L75-L102)) | | | ✅ | | | ✅ | | | ❌ none | ~~| [`godns`](https://github.com/TimothyYe/godns#supported-dns-providers) | | | | | |~~ - judgement: given this compatibility matrix, the path of least resistance to automating DNS would seem server `bind` (optionally with client octodns (thru TF / NixOS-DNS)) or (given a nix package/module, possibly thru ngipkgs) deSEC. - ~~as an alternative to interfacing with upstream DNS providers, we could initially presume hosting providers would have registrar status (pilot with ProcoliX: [EURid](https://eurid.eu/) registrar), significantly reducing the number of potential upstreams to interface with.~~ - ~EURid has a €2500 signup fee, lacks public API documentation, and ProcoliX [isn't a registrar](https://eurid.eu/en/get-your-eu/find-a-registrar/?country=NL&retailer=true) with them so far, tho EURid's interface [is like EPP](https://claude.ai/share/d07077db-805c-4270-b6f0-276340fda40d)~ - ~[metaregistrar](https://metaregistrar.com/apidocs/) (dutch commercial entity, TF DNS challenge [1](https://registry.terraform.io/providers/vancluever/acme/latest/docs/guides/dns-providers-metaregistrar) [2](https://registry.terraform.io/providers/binlab/acme/latest/docs/guides/dns-providers-metaregistrar)) was suggested by procolix as a registrar that serves many registries, for short-term demo purposes (with long-term intent to instead do an open-source registrar connecting many registries). (for what it's worth, this registrar appears not currently suggested by any of our listed DNS clients.)~ - seems not as convenient so far as the automation already available for the below - [opusdns](https://www.opusdns.com/) (DE, not for individual consumers) offers a [TF provider](https://registry.terraform.io/providers/OpusDNS/opusdns/latest/docs/resources/domain) for domain registration, while for DNS seeming covered by **octodns**. as such, this might make for one easy way for us to get going in an automation-friendly manner. 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 a new dependency

2025-02-11 14:26:35 +01:00

#76 Deployed services are accessible

kiara removed a dependency

2025-02-11 15:15:48 +01:00

#76 Deployed services are accessible

kiara added a new dependency

2025-02-11 15:16:18 +01:00

#76 Deployed services are accessible

kiara added a new dependency

2025-02-11 16:22:32 +01:00

#118 Relevant email accounts are provisioned such that the operator may be contacted

fricklerhandwerk removed a dependency

2025-03-14 11:44:49 +01:00

#76 Deployed services are accessible

kiara added this to the Fediversity project

2025-04-18 10:21:02 +02:00

kiara referenced this issue

2025-04-30 09:17:41 +02:00

Have a way to make requests to the DNS service so that subdomains can be pointed to the right IP #109

fricklerhandwerk commented

2025-04-30 14:13:40 +02:00

Owner

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?

👍 1

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 added the

type: user story

label

2025-05-01 12:21:36 +02:00

kiara added a new dependency

2025-05-01 16:30:14 +02:00

#104 Have a DNS service running to allow users to tie services to their own domain

kiara referenced this issue

2025-05-01 16:54:28 +02:00

button works deployed #307

kiara removed this from the Fediversity project

2025-06-10 19:07:00 +02:00

kiara referenced this issue

2025-09-11 19:23:41 +02:00

Start deployment migration #78

kiara added a new dependency

2025-09-11 19:23:58 +02:00

#78 Start deployment migration

kiara added a new dependency

2025-09-11 19:24:36 +02:00

#100 migrating application data between hosting providers

kiara referenced this issue

2025-09-11 19:25:02 +02:00

migrating application data between hosting providers #100

kiara added a new dependency

2025-09-11 20:37:02 +02:00

#99 applications deployed on command

kiara referenced this issue

2025-09-11 20:37:36 +02:00

applications deployed on command #99

kiara added this to the Fediversity project

2025-11-04 19:34:50 +01:00

kiara removed a dependency

2025-11-07 19:39:06 +01:00

#104 Have a DNS service running to allow users to tie services to their own domain

kiara referenced this issue

2025-11-07 19:40:27 +01:00

Have a DNS service running to allow users to tie services to their own domain #104

kiara referenced this issue

2025-11-08 18:28:31 +01:00

allow handling DNS by octodns #579

kiara referenced this issue from a commit

2025-11-09 00:14:28 +01:00

allow handling DNS by octodns (#579)

kiara referenced this issue

2025-12-03 01:40:11 +01:00

Have a DNS service running to allow users to tie services to their own domain #104

kiara added the

13 points

label

2025-12-03 01:40:30 +01:00

kiara referenced this issue

2026-02-04 10:35:11 +01:00

reproduce DNS VM #200

kiara referenced this issue

2026-02-22 12:41:09 +01:00

port infra to terraform #309

~~kiara referenced this issue 2026-04-22 11:10:48 +02:00~~

unit-tested functionality integrated in deployment pipelines #833

kiara added a new dependency

2026-06-07 18:19:10 +02:00

#954 demo env broken

kiara added the

ambition/install-applications

label

2026-06-11 15:51:29 +02:00

kiara referenced this issue

2026-07-04 15:01:54 +02:00

reproduce DNS VM #200

kiara commented

2026-07-06 11:32:34 +02:00

Author

Owner

a new idea suggested by @koen is to check up with eurid on whether they might have a testing environment available for us

edit: actually, that would not result in actual domains, so wouldn't really help to test more than just that one bit, rather than our whole application

a new idea suggested by @koen is to check up with eurid on whether they might have a testing environment available for us edit: actually, that would not result in actual domains, so wouldn't really help to test more than just that one bit, rather than our whole application