caddy-ipv64

DNS-01 provider plugin for Caddy that works with ipv64.net DNS hosting.

Installation

Build with xcaddy:

xcaddy build --with github.com/Sickjuicy/caddy-ipv64

Quick Start

1. Set your API token:

export IPV64_API_TOKEN="your_token_here"

2. Create a Caddyfile:

example.yourdomain.ipv64.de {
  tls {
    dns ipv64 {
      api_token {env.IPV64_API_TOKEN}
    }
  }
  respond "Hello World!"
}

3. Run Caddy:

caddy run

Configuration Examples

Single Domain

app.yourdomain.ipv64.de {
  tls {
    dns ipv64 {
      api_token {env.IPV64_API_TOKEN}
    }
  }
  respond "My app"
}

Wildcard Certificate

*.yourdomain.ipv64.de {
  tls {
    dns ipv64 {
      api_token {env.IPV64_API_TOKEN}
    }
  }
  respond "Wildcard works"
}

Global Provider

{
  acme_dns ipv64 {
    api_token {env.IPV64_API_TOKEN}
  }
}

app1.yourdomain.ipv64.de {
  respond "App 1"
}

app2.yourdomain.ipv64.de {
  respond "App 2"  
}

Configuration Options

Option	Default	Description
api_token	required	Your ipv64.net API token
create_delay_seconds	25	DNS propagation wait time

Requirements

• Domain hosted on ipv64.net
• Subdomain must exist in your DNS panel
• Valid API token

Testing

Use staging CA for testing:

{
  acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
}

test.yourdomain.ipv64.de {
  tls {
    dns ipv64
  }
  respond "Testing"
}

Troubleshooting

Certificate fails: Check your API token and verify subdomain exists.

DNS errors: Increase create_delay_seconds to 30 or higher.

Rate limits: Use Let's Encrypt staging for testing.

Enable debug logging:

caddy run --config Caddyfile --debug

License

License