Add Namecheap & Spaceship as DNS Providers

What problem will this feature address?

Dokploy DNS automation currently supports only a limited selection of DNS providers. Users who manage their domains through Namecheap or Spaceship cannot currently connect those DNS accounts directly to Dokploy.

As a result, when deploying an application with a domain managed by either provider, users have to manually leave Dokploy, open their registrar's DNS management panel, and create or modify the required records themselves.

This adds an unnecessary manual step to the deployment workflow and becomes particularly inconvenient for users managing multiple domains and applications.

Describe the solution you'd like

Add Namecheap and Spaceship as DNS providers in Dokploy.

Both integrations should use the existing DnsClient interface in:

packages/server/src/utils/dns/

This would keep both providers consistent with Dokploy existing DNS provider architecture rather than introducing a separate implementation or workflow.

For Namecheap, the integration should use the Namecheap API to authenticate the account and manage DNS configuration. It should support the DNS operations required by Dokploy, including discovering the appropriate domain/zone, retrieving existing records, and creating, updating, and deleting records.

For Spaceship, the integration should use the Spaceship API and API credentials to provide the same core DNS functionality required by Dokploy, including accessing the relevant domain/zone and managing its DNS records.

At a minimum, both providers should support the operations needed by the existing DnsClient abstraction:

-Discovering the appropriate DNS zone/domain
-Listing existing DNS records
-Creating DNS records
-Updating existing DNS records
-Deleting DNS records
-Authenticating securely using the provider's API credentials

Once the provider credentials are configured, users should be able to select Namecheap or Spaceship in Dokploy and have the DNS records required for their applications managed automatically.

The goal is to make connecting a domain from either provider part of the normal Dokploy deployment workflow, without requiring users to manually copy DNS values between different dashboards.

Describe alternatives you've considered

The current workaround is to manually take the DNS information generated or required by Dokploy and create the corresponding records in the Namecheap or Spaceship dashboard.

Although this works, it introduces an additional manual step every time DNS configuration is required and becomes tedious when managing multiple applications or domains.

Another alternative is to move DNS management to Cloudflare, AWS Route53, Porkbun, or another currently supported provider. However, this is not an ideal solution for users who already have their domains and DNS infrastructure established with Namecheap or Spaceship.

Users should not need to migrate their DNS provider simply to take advantage of Dokploy domain automation.

Additional context

Supporting both Namecheap and Spaceship would significantly expand Dokploy DNS provider coverage and make the platform more convenient for users managing domain portfolios.

Namecheap is an established domain registrar with a large number of existing domain users, while Spaceship is a newer registrar that is increasingly used for domain registration and portfolio management.

Native support for both would allow users to keep their existing domains where they are while still benefiting from Dokploy automated deployment and DNS workflow.

The implementation should ideally follow the same provider pattern already established in the codebase, making both integrations maintainable and consistent with the existing DNS architecture.

Will you send a PR to implement it?

No

Start in packages/server/src/utils/dns/ by reading the DnsClient interface and existing provider implementations. Review the Namecheap and Spaceship API requirements, then define the integration scope around authentication, zone discovery, and record listing, creation, updating, and deletion. Done means both providers can be selected and manage Dokploy-required DNS records through the existing workflow.