deSEC signs the zones it serves and manages their signing keys. Domain Nexus exposes that provider behaviour rather than pretending it can turn a deSEC zone into an unsigned one. Use the service within its current delegation and account conditions, and keep the registrar's DS configuration aligned with the active DNS provider.
IN THIS ARTICLE
01 Prepare a suitable token
Create an authorised deSEC API token for the intended domains. Review its high-level domain creation and deletion permissions separately from its record-set policies. A token restricted to an existing TXT record may work for certificate validation but cannot manage a whole hosting zone.
Use policies that match the operational scope. A deliberately restricted token should not also receive unnecessary token-management powers. Where you need new zones created automatically, ensure the credential and applicable policies permit both zone creation and the subsequent record changes.
02 Connect and test
- Add a Domain Nexus server and choose deSEC (DNSSEC by default).
- Paste the secret into API token.
- Leave API URL at the normal service default. A different self-hosted endpoint requires a separately authorised supported configuration.
- Save, run the check and read an owned zone.
- Test a temporary TXT update and compare the provider state. Prepare the actual deSEC nameserver delegation in accordance with the service's requirements.
- Read the zone's DNSSEC information and publish the matching parent DS when establishing the validation chain.
Why can I not switch DNSSEC off?
The provider signs its zones by design, and the adapter reports that limitation. If you need an unsigned authoritative backend, plan a provider migration. Remove or update the parent DS in the appropriate order and allow its cached state to expire before relying on a differently signed or unsigned replacement.
Can I use deSEC as an undelegated spare copy?
Review the provider's service conditions before using it as a passive replica. This adapter does not expose secondary-zone operation. Domain Nexus's multi-server synchronisation does not override a provider's conditions or make a hidden copy an authorised use of the service.
If a request is rejected, distinguish token policies, account limits and DNS validation problems. Keep the current provider records intact while diagnosing access.