Skip to content
nsin docs

Domain Modes (Managed vs External)

nsin connects to your domain in two modes:

  • Managed DNS — nsin runs your DNS. Easiest.
  • External DNS — you keep DNS at your provider and point it at nsin.

Switch modes later in domain settings.

Managed DNSExternal DNS
Who runs your DNSnsinYou
How you connectChange your nameserversAdd A/CNAME records
Ownership checkAutomaticOne CNAME record
SSLFree & automaticFree & automatic (once verified)
Best forMost peopleKeeping DNS at your provider

Point your nameservers to nsin; it then handles records and security.

  1. Add your domain and choose Managed DNS.
  2. Copy the two nameservers nsin gives you.
  3. Replace your old nameservers with them at your provider. See Nameservers.
  4. Wait — usually minutes, up to 24–48 hours.

You get auto-activation, free auto-renewed SSL (see SSL Overview), and records managed inside nsin (see Managing DNS Records).

You keep DNS at your provider; nsin sits in front as a proxy.

  1. Add your domain and choose External DNS.
  2. Verify ownership: add the CNAME record nsin gives you (a host and a target) at your provider.
    • nsin checks automatically every 5 minutes, or check manually (once a minute).
    • You have a 3-day window to verify.
    • Keep the record afterwards — it connects you to nsin, like nameservers on a Managed domain.
  3. Once verified, add the A or CNAME records nsin gives you.
  4. SSL is automatic once verified. For your own certificate, upload it with its private key in the SSL section and pick its hostnames.

Remove or change the verification record later and the domain counts as moved away: it serves 3 more days, then is disabled. Put it back to reactivate.

Domains on the older TXT record keep working on their own certificates; add the new record for automatic SSL. You manage records at your provider, not inside nsin.

Your dashboard labels the domain Managed DNS (blue) or External DNS (plain). Change modes anytime in domain settings.

I switched to External and my site shows “Not Secure”. Check you uploaded a valid certificate and its private key, covering the hostname you’re visiting. See SSL Overview.