DynIP launches with RFC 2136, IPv6, and DNSSEC support

DynIP has launched a dynamic DNS service supporting RFC 2136, IPv6, and DNSSEC, targeting infrastructure engineers managing dynamic IP environments [DynIP]. The platform enables automated DNS record updates via standard-compliant clients, eliminating reliance on proprietary agents. Users can authenticate updates using TSIG keys, ensuring secure zone modifications without exposing DNS servers to untrusted sources.

The service natively supports IPv6, allowing dual-stack deployments where both A and AAAA records update in parallel. DNSSEC signing is enabled at the zone level, with trust chains publishable through registrar interfaces — a rarity among dynamic DNS providers. By adhering to RFC 2136, DynIP integrates with existing tooling like nsupdate, BIND, or dnsmasq, reducing migration friction.

Unlike consumer-grade alternatives, DynIP allows bring-your-own-device (BYOD) configurations, meaning users deploy update logic on their own hardware or containers rather than relying on vendor-hosted agents. This model suits environments requiring audit control or air-gapped operations.

DynIP’s approach contrasts with Cloudflare’s API-driven model or AWS Route 53’s dependency on AWS-hosted clients. While those platforms dominate at scale, they often require vendor lock-in or custom scripting. DynIP fills a niche for teams needing standards-based, self-managed update paths with cryptographic integrity.

The company states that full zone transfers (AXFR/IXFR) are in development, which would allow secondary DNS setups with automatic sync from dynamic primaries [DynIP].