feat: add namecom protocol for Name.com DNS#935
Open
beadon wants to merge 2 commits into
Open
Conversation
Adds a new 'namecom' protocol for updating DNS records via the Name.com API v4, with HTTP Basic auth, GET-then-PUT/POST logic, IPv4/IPv6 support, apex domain handling, and 13 test cases covering success, update, error, and no-op scenarios. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3987ce6 to
88cde09
Compare
Contributor
Author
|
Rebased onto current main. Conflicts resolved (ChangeLog, Makefile, ddclient.conf.in, ddclient.in @needs_json). Ready to merge. |
Bare FQDN server defaults send requests over plain HTTP without ssl=1; the API requires HTTPS and rejects plain HTTP with 401. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Adds a new
namecomprotocol for updating DNS A/AAAA records via the Name.com API v4.login= Name.com username,password= API token)/v4/domains/{zone}/recordsto list, then PUT (update existing) or POST (create new)hoststring), configurable TTL (default 300)messagefield from JSON bodynamecomadded to@needs_jsonininit_configFiles changed
ddclient.in—%protocolsentry,@needs_json,nic_namecom_examples(),nic_namecom_update(),_namecom_call()t/protocol_namecom.pl— 13 subtestsMakefile.am— test added tohandwritten_testsREADME.md— Name.com listed alphabeticallyddclient.conf.in— example config blockChangeLog.md— entry under## v4.0.1-rc.2 (unreleased work-in-progress)Test plan
make check TESTS=t/protocol_namecom.pl VERBOSE=1— all 13 subtests passmake check— full suite passes (895 pass, 2 skip)namecomappears alphabetically in%protocols(betweennamecheapandnfsn)namecomin@needs_json(betweenhetznerandnfsn)🤖 Generated with Claude Code