I'm Daniel, network engineer in Sweden
I'm Daniel, network engineer in Sweden. Built DynIP because every DDNS service I tried was designed around 2010-era networks: proprietary HTTP-only update protocols, poor IPv6, no DNSSEC, little support for actuallymodern devices. What's in it: - RFC 2136 / TSIG updates as a first-class path. FortiGate genericDDNS and MikroTik's /tool dns-update work natively — no custom client needed. HTTP API is also available for everything else. - IPv6 end-to-end. Authoritative nameservers reachable over IPv6 (with AAAA glue published at the parent .dev zone), customer zones publish A and AAAA, and the platform works for IPv6-only clients. - DNSSEC available on selected zones. With a single toggle. - Bring your own domain via subdomain delegation. Point subdomain.yourcompany.com at our nameservers, manage normally. - Hidden primary architecture: two geographically distributed secondaries (Sweden + Switzerland) verify TSIG locally and forward updates to a primary that doesn't take public traffic. …
Original discussionDynIP – Dynamic DNS with RFC 2136, IPv6, DNSSEC, and BYOD128 source comments · at import