🦞 DDNS Skill

Update your dynamic DNS records on demand. Detects public IP changes and pushes them to your DDNS provider (dynv6 by default). No periodic cron needed — run it when you suspect your IP has changed.

Quick start

1️⃣ Create the config file

Outside the skill directory, in your home config folder:

mkdir -p ~/.config/picoclaw-ddns

cat > ~/.config/picoclaw-ddns/config.json <<'EOF'
{
  "provider": "dynv6",
  "dynv6": {
    "hostname": "yourname.dynv6.net",
    "token": "your-http-token"
  }
}
EOF

chmod 600 ~/.config/picoclaw-ddns/config.json

🔒 Why chmod 600? The token is sensitive — only the file owner should read it. The config lives in ~/.config/picoclaw-ddns/, not inside the skill folder, so it won't be accidentally bundled or published.

2️⃣ Run the update

bash <workspace>/skills/ddns-updator/scripts/ddns.sh

The script will:

1. Detect your current public IPv4 and IPv6 addresses
2. Compare against the last-known addresses
3. Only call the dynv6 API if something changed
4. Save the new addresses to ~/.config/picoclaw-ddns/state.json

3️⃣ Just check your IP (no update)

bash <workspace>/skills/ddns-updator/scripts/get_ip.sh

Scripts

Configuration reference

Config file (~/.config/picoclaw-ddns/config.json)

{
  "provider": "dynv6",
  "dynv6": {
    "hostname": "yourname.dynv6.net",
    "token": "your-http-token"
  }
}

Environment variables (alternative to config.json)

If both config.json and env vars are present, env vars take precedence.

State file (~/.config/picoclaw-ddns/state.json)

Auto-managed. Records the last-known IPs so the next run can detect changes.

{
  "ipv4": "203.0.113.1",
  "ipv6": "2001:db8::1",
  "updated": "2025-07-05T12:00:00+08:00"
}

Triggering via the agent

Just say:

"Update my DDNS" "Check and update my DNS" "What's my public IP?" "Run DDNS check"

The agent will read this skill and execute scripts/ddns.sh for you.

Scheduled / periodic updates (optional)

Add a crontab entry for fully automatic updates:

# Every 10 minutes
*/10 * * * * /bin/bash /path/to/ddns.sh

Or every hour:

# Every hour at minute 0
0 * * * * /bin/bash /path/to/ddns.sh

Multi-domain support

Run the orchestrator with different config files:

CONFIG_FILE=~/.config/picoclaw-ddns/domain1.json bash scripts/ddns.sh
CONFIG_FILE=~/.config/picoclaw-ddns/domain2.json bash scripts/ddns.sh

Extending to other providers

The references/providers.md file documents the APIs for:

• dynv6 (current default)
• DuckDNS
• Cloudflare (v4 API)
• No-IP

To add a new provider, add a new scripts/update_<provider>.sh script following the same parameter convention as update_dynv6.sh, then update the main script to dispatch based on config.json → .provider.

Architecture

User says "Update my DDNS"
        │
        ▼
  Agent reads this SKILL.md
        │
        ▼
  Executes scripts/ddns.sh
        │
        ├── scripts/get_ip.sh
        │       └── curl https://api.ipify.org           → IPv4
        │       └── curl https://api64.ipify.org          → IPv6
        │
        ├── Compare with ~/.config/picoclaw-ddns/state.json
        │
        └── If changed:
            └── scripts/update_dynv6.sh <hostname> <token> <ipv4> <ipv6>
                    └── GET https://dynv6.com/api/update?...

Security notes