SimpleACME
Sign inCreate account →
Private services

Trusted certificates for a private NAS with DNS-01

Use an external ACME client and SimpleACME DNS validation for private Synology or QNAP names, then import and verify certificates through supported vendor workflows.

A NAS management interface often belongs behind a firewall or VPN. Publishing an extra HTTP challenge route just to renew its certificate may be the wrong tradeoff. DNS-01 allows you to validate a public DNS name while keeping the NAS itself private.

SimpleACME makes that option easier when you do not want a DNS-provider API token on the NAS or renewal host. Add the permanent challenge CNAME, issue through an external ACME client, and use the NAS vendor's supported certificate-import process.

Pick the name and deployment boundary

Use a public DNS name you control, such as nas.example.com. Your internal resolver can direct it to a private address, but the challenge name must still resolve correctly for the public validator.

Decide whether issuance belongs on the NAS or on a separate managed host. A separate host can centralize the ACME client, credentials and monitoring. It also creates a deployment step that must be reliable and protected.

Prepare the delegated challenge

Create single-domain or wildcard coverage in SimpleACME and verify the supplied CNAME. Configure an existing registration in your chosen client; do not assume an appliance's ACME feature supports arbitrary external DNS hooks.

The public integration pattern works with Traefik, win-acme or Certbot when used in their supported environments. The NAS receives the resulting certificate in the format and chain arrangement required by its own documentation.

Keep import and assignment visible

Importing certificate material may not automatically assign it to every NAS service. Review the selected certificate for the management interface and any other services that need it. Avoid copying a wildcard private key to applications that do not require it.

When automating import, use a supported vendor interface and the least access it needs. Treat undocumented endpoints and commands as maintenance responsibilities, not guaranteed permanent integrations supplied by SimpleACME.

Check the entire renewal

  1. Complete a staging validation before production issuance.
  2. Request the real certificate and retain the expected chain.
  3. Import through the supported NAS workflow.
  4. Assign it to the intended service.
  5. Reconnect with the real hostname and check the certificate being served.
  6. Schedule renewal and verify that the deployment step runs unattended.

The advantage is that validation no longer requires opening the NAS's HTTP service to the internet or maintaining a provider-specific DNS token there. SimpleACME handles the delegated TXT updates; your client and NAS remain responsible for issuance and installation. The service overview and FAQ explain those boundaries before you choose the workflow.

KEEP EXPLORING

A little more clarity.

ONE CNAME. A REPEATABLE WORKFLOW.

Your next certificate. A little less complicated.

Keep your DNS provider and your ACME client.
Prepare your domain before activating paid updates.

Create your account →Explore the integrations