Skip to main content

Module dns

Module dns 

Source
Expand description

The DNS management interface (epic #1158, ticket #1162 / Phase A3).

hyprstream defines this interface; it does not depend on any specific DNS implementation. Managed DNS (PowerDNS, Route53, Cloudflare, a hand-rolled RFC 2136 client, an out-of-process HTTP webhook, …) is a product layer above hyprstream — if this crate ever required a particular DNS server, self-hosters could not run it.

Two jobs flow through this trait:

  1. ACME DNS-01 challenge responses — publish/delete a TXT record at the _acme-challenge.<apex> owner name so a public CA can validate the *.<apex> wildcard certificate.
  2. Wildcard address records — publish wildcard A/AAAA for the delegated zone so alice.<apex> resolves to the hyprstream node. The wildcard covers exactly one label (the A2 depth invariant; see crate::account::zone).

The credential a deployment hands to its DnsProvider implementation must be zone-scoped — able to write records only inside the delegated account zone and nowhere else. The plan is explicit: do not hand a zone-wide DNS credential to the ACME client.

Structs§

UnconfiguredDnsProvider
Fail-closed no-op provider used when a deployment wires no DNS backend.

Enums§

DnsError
A DNS operation failed. Implementations wrap their backend’s native error.

Traits§

DnsProvider
The interface a deployment’s DNS management layer implements.