Skip to content

Conversation

@chicks-net
Copy link
Collaborator

Summary

Fixes #3965

Investigation revealed that DigitalOcean's SOA support is too limited to be useful in DNSControl:

  • While the API documentation mentions SOA records exist, only the TTL can be modified
  • The SOA record cannot be deleted
  • This makes it impractical to manage via DNSControl

Changes made:

  • Disabled CanUseSOA capability in the DigitalOcean provider (with comment "despite docs")
  • Updated provider documentation to remove SOA from supported record types
  • Added clarification explaining why SOA is not supported
  • Updated the provider feature matrix table to reflect SOA is not supported

Test plan

  • Reviewed the DigitalOcean API documentation
  • Confirmed the limitation matches the test failures from CHORE: Update dependencies #3963
  • Updated all relevant documentation files
  • Provider capability correctly set to Cannot()

🤖 Generated with Claude Code

Investigation revealed that DigitalOcean's SOA support is too limited to be
useful - while the API documentation mentions SOA records exist, only the TTL
can be modified and the record cannot be deleted. This makes it impractical
to manage via DNSControl.

This PR re-disables SOA support (which was disabled in StackExchange#3963) and updates
the documentation to clarify why SOA is not supported.

Fixes StackExchange#3965

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
@tlimoncelli tlimoncelli merged commit fc8a508 into StackExchange:main Jan 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DIGITALOCEAN: SOA support?

2 participants