Skip to content
HN On Hacker News ↗

DynIP — Dynamic DNS that actually works

▲ 341 points 128 comments by dynip 3mo ago HN discussion ↗

Pangram verdict · v3.3

We believe that this document is a mix of AI-generated, and human-written content

60 %

AI likelihood · overall

Mixed
41% human-written 59% AI-generated
SEGMENTS · HUMAN 1 of 3
SEGMENTS · AI 2 of 3
WORD COUNT 371
PEAK AI % 100% · §2
Analyzed
May 26
backend: pangram/v3.3
Segments scanned
3 windows
avg 124 words each
Distribution
41 / 59%
human / AI fraction
Verdict
Mixed
Pangram v3.3

Article text · 371 words · 3 segments analyzed

Human AI-generated
§1 Human · 12%

dynip.dev Authoritative Control Plane {{ activeUser.email }}

Quick Start Guide {{ showHelp ? 'Hide' : 'Show' }} 1. Create a Zone: Type your device name, select your preferred base domain, and click Create Zone. 2. Get the Config: Click the Snippets button next to your new domain. 3. Deploy: Select your device type and copy the generated configuration block directly into your router's CLI. Note: IPv4 and IPv6 (Dual-Stack) are detected and updated automatically based on the incoming connection.

.

Domain & Tools Current IP TSIG Secret DNSSEC SSL Cert {{ zone.name }} ⚠ Locked

{{ zone.ip }} Sync: {{ formatSyncTime(zone.last_sync) }}

{{ certDaysLabel(zone) }}

No domains registered. Create one above to get started.

Quick Sync {{ showSync ? 'Hide' : 'Show' }}

Instantly update your selected zones to match this device's current external IP address.

📡 Detected Network IP {{ mobileIp || 'Detecting...' }}

{{ zone.name }} {{ zone.ip }} No zones available. Create one above.

API Automation {{ showApi ? '

§2 AI · 100%

Hide' : 'Show' }}

Quick test (uses your session — expires when you log out) Programmatically register new zones with your current session token. Send a POST request to the /register endpoint. curl -X POST "{{ backendUrl }}/register?subdomain=my-new-router&base_domain={{ baseDomains[0] }}" \ -H "Authorization: Bearer {{ token }}" Session tokens expire on logout — use an API token below for long-running automation.

API tokens (Pro+)

API tokens are a Pro feature Long-lived tokens for automation: monitoring scripts, CI pipelines, MSP integrations. Tokens don't expire when you log out. Upgrade to Pro →

Long-lived tokens for automation. Each token can be scoped read-only or full access, and revoked at any time. Loading tokens… No API tokens yet. Create one to get started. Name Token Scope Last used Expires Action {{ t.name }} {{ t.token_prefix }} {{ t.scope === 'read' ? 'Read-only' : 'Full' }} {{ t.last_used_at ? formatPlanDate(t.last_used_at) : 'Never' }} {{ t.expires_at ? formatPlanDate(t.expires_at) : 'Never' }}

New API Token Tokens are shown once at creation — store them in a password manager or secrets vault. Name Scope Read-only Full access Expires {{ apiTokenModal.error }}

⚠ Save this token now This token won't be shown again. Store it somewhere secure (1Password, Bitwarden, your CI's secrets manager).

§3 AI · 100%

{{ apiTokenModal.created.token }}