mholt/caddy-dynamicdns

Using multiple providers

Closed

#47 opened on Jul 14, 2023

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Go (38 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (365 stars)
PR merge metrics
 (Avg merge 3d 13h) (1 merged PR in 30d)

Description

Is it possible to use multiple providers to update different domains? I tried this config (simplified)

{
    dynamic_dns {
        provider cloudflare {$CLOUDFLARE_API_TOKEN}
        domains {
            main-domain.com
        }
    }

    dynamic_dns {
        provider duckdns {$DUCKDNS_TOKEN}
        domains {
            secondary-domain.com
        }
    }
}

but it seems like only the second dynamic_dns block (for DuckDNS) is functional; main-domain.com is not updated at all.

Contributor guide

Research direction
Investigate how caddy dynamicdns processes multiple dynamic dns blocks. Check if the second block overwrites the first due to struct reuse or map key collision. Look at the provider initialization and domain update logic.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoCaddy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55