How uDDNS keeps a hostname current

How uDDNS keeps a hostname current An architecture diagram generated by Archify. HTTPS address services · Public IPv4 / IPv6 · Architecture component HTTPS address services Public IPv4 / IPv6 DNS fallback · Optional · off by default · Architecture component DNS fallback Optional · off by default Address discovery · Validate and pin HTTPS · Computer running uDDNS Address discovery Validate and pin HTTPS Configuration · Accounts, hosts, interval · Computer running uDDNS Configuration Accounts, hosts, interval uDDNS update loop · Compare before writing · Computer running uDDNS · explicit scope uDDNS update loop Compare before writing explicit scope DNS provider API · Selected host records · Architecture component DNS provider API Selected host records CLI and MCP · Validate, preview, confirm · Computer running uDDNS CLI and MCP Validate, preview, confirm State and history · Atomic per-host checkpoints · Computer running uDDNS State and history Atomic per-host checkpoints Notifications · Webhook, ntfy, Slack, Discord · Architecture component Notifications Webhook, ntfy, Slack, Discord HTTPS address check only when enabled validated address validated hosts and policy HTTPS update if changed preview or confirmed action result and checkpoint redacted outcome Computer running uDDNS Legend Frontend Backend Database Cloud Security External

Normal cycle

  • • Discover the public address
  • • Compare it with saved state
  • • Contact the provider only after a change

Network safety

  • • Validate HTTPS targets before connecting
  • • Pin requests to the verified address set
  • • Keep the plain-DNS fallback off by default