Add checkdomain.de DDNS provider support #526
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for checkdomain.de as a DDNS provider, implementing their REST API integration as mentioned in the issue comments.
Changes Made
pkg/ddns/providers/checkdomain.go
with full REST API supportupdate.go
.gitignore
to prevent committing build artifacts and temporary filesImplementation Details
The checkdomain.de provider follows the established patterns used by other REST API-based providers in the codebase:
API Structure
The provider accepts the following configuration parameters:
APIToken
: Bearer token for authenticationDomain
: The domain to updateRecordName
: The DNS record name (subdomain)RecordType
: DNS record type (defaults to "A")TTL
: Time-to-live value (defaults to 3600 seconds)Testing
go vet
andgo fmt
checksThe implementation is ready for use and can be extended with additional API features as needed based on the full checkdomain.de API documentation.
Fixes #15.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.