Skip to content
privatenpmREGISTRY
Start free trial
Menu

Verify a custom npm registry domain

A custom domain gives customers a familiar registry URL. DNS ownership and certificate readiness must be confirmed before installs use it.

Request a hostname

Create a private registry, then open Registry → Domains and request its hostname, such as npm.acme.com. The domain page shows a fresh ownership challenge and its expiry. Keep that page available while changing DNS.

Verify a registry hostname form with an npm.acme.com example
Request the hostname before adding its DNS records.

Publish the DNS records

  1. Add the TXT record shown on the domain page at _privatenpm-challenge.npm.acme.com. Copy its value exactly; it is unique to your request.
  2. Point the registry hostname at the edge target provided for your installation using a CNAME. DNS providers may display the record name relative to your zone, so check the final fully qualified name.
  3. Return to the domain page to check verification and certificate status. Background verification continues while the challenge is valid. Wait until the domain is active and its certificate is ready before giving customers that URL.

If the challenge expires or the page reports failure, inspect the public TXT answer and request a fresh challenge through the domain management flow. Once active, update .npmrc to use the custom host for both the scoped registry and token line. See the configuration examples.

READY WHEN YOU ARE

Put private packages to work.

Start 30-day trial