Hostnirvana Support
Control Panel →

Hostnirvana Support Docs

Here you can find all the help documents and tutorials

How to use Cloudflare with Hostnirvana?

February 3, 2026 — hnsupport

Yes — you can use Hostnirvana services while keeping your domain on Cloudflare (including on their free plan). From the Hostnirvana side, changing nameservers is not mandatory for hosting; it’s only required if you want Hostnirvana/StackDNS to be the authoritative DNS provider for the domain.

Is it possible to use Hostnirvana services while continuing to use Cloudflare?

  • Web hosting on Hostnirvana: Yes. Keep Cloudflare nameservers, and create/adjust the required DNS records in Cloudflare to point to your Hostnirvana hosting.
  • Email on Hostnirvana (mailboxes): Yes. Keep Cloudflare nameservers, and set the MX (and related SPF/DKIM/DMARC TXT) records in Cloudflare to the values Hostnirvana provides for your service.
  • SSL: Yes. If Cloudflare is proxying the website, Cloudflare will present SSL to visitors and connect back to your Hostnirvana hosting as the “origin”. Hostnirvana can still provide an origin certificate (AutoSSL), but the exact Cloudflare SSL mode you choose affects how that connection is validated.

Note- If you want to use our free SSL then you have to use Hostnirvana’ s nameservers.

If changing name servers is required, are there any alternatives or workarounds?

Option A: Keep Cloudflare nameservers (most common)

Step 1: Point the website to Hostnirvana

  • Create the required A/AAAA/CNAME records in Cloudflare that point your root domain and www to your Hostnirvana hosting.
  • If you enable Cloudflare proxying for the website, that’s fine for HTTP/HTTPS traffic; it does not “proxy” things like FTP/SMTP/IMAP in the same way.

Step 2: Point email to Hostnirvana (only if you’re using Hostnirvana mail)

  • Add the MX records exactly as provided by Hostnirvana for your domain/service.
  • Add/maintain email authentication records:
  • SPF (TXT)
  • DKIM (TXT — values provided by Hostnirvana when DKIM is enabled)
  • DMARC (optional but recommended)

Step 3: Confirm SSL expectations

  • If Cloudflare is proxying the site, visitors see Cloudflare’s certificate; the connection from Cloudflare to Hostnirvana should ideally use a valid certificate on the Hostnirvana side (Hostnirvana AutoSSL typically covers this).

Option B: Move DNS to Hostnirvana (StackDNS nameservers)

This is only needed if you want Hostnirvana to manage DNS directly (e.g., fully managing records in one place, automatic DNS linking to Hostnirvana services, etc.).

Step 1: Change nameservers at the domain registrar

  • Hostnirvana StackDNS nameservers are:
  • ns1.stackdns.com
  • ns2.stackdns.com
  • ns3.stackdns.com
  • ns4.stackdns.com

Step 2: Manage DNS in Hostnirvana

If the domain is registered with Hostnirvana, nameserver changes are managed here: Domains

Hosting services are listed here: Hosting

Quick recommendation

  • If you specifically want Cloudflare’s DNS/proxy features: keep Cloudflare nameservers and just point the required records to Hostnirvana.
  • If you want “all DNS inside Hostnirvana”: switch to StackDNS nameservers.


Please check Step-by-step: Use Cloudflare nameservers with Hostnirvana

Step 1: Confirm what you’re pointing to Hostnirvana

Decide which of these you’re using on Hostnirvana, because the DNS records differ:

  • Website hosting on Hostnirvana (most common)
  • Email/mailboxes on Hostnirvana
  • Both website + email on Hostnirvana

Step 2: Collect the DNS values from Hostnirvana that you will copy into Cloudflare

Use these Hostnirvana pages to locate the correct values for your specific service(s):

Hosting packages list:
Domains list (if the domain is with Hostnirvana):

What you typically need to copy (depending on your setup):

  • Website hosting
  • The destination for @ (root domain) and www (either an IP for an A record, or a target hostname for a CNAME, depending on how your package is set up)
  • Email hosting (if using Hostnirvana mailboxes)
  • MX records
  • SPF TXT record
  • DKIM TXT/CNAME records (if DKIM is enabled)
  • Optional DMARC TXT record

Step 3: In Cloudflare, open the DNS records for your domain

In Cloudflare, go to the domain and open DNS (the place where you add A/CNAME/MX/TXT records).

Step 4: Point your website (root and www) to Hostnirvana

Add/update records for the website.

Common patterns (use the one that matches what Hostnirvana provides you in Step 2):

  • Root domain (@)
  • A record: @ → <Hostnirvana hosting IPv4 address>
  • If you also have IPv6 on the package and you want it: AAAA record: @ → <Hostnirvana IPv6 address>
  • WWW (www)
  • CNAME: www → @
  • Or CNAME: www → <hostname provided by Hostnirvana>

Important Cloudflare setting while testing:

  • Set the website records to DNS only (grey cloud) initially to confirm it loads correctly, then you can switch to Proxied (orange cloud) if you want Cloudflare’s CDN/proxy features.

Step 5: Configure SSL/TLS in Cloudflare for a Hostnirvana-hosted site

This is on the Cloudflare side under SSL/TLS.

  • Avoid “Flexible” for a typical hosting setup, because it commonly causes redirect loops or insecure origin connections.
  • Prefer “Full (strict)” if your Hostnirvana site has a valid certificate at the origin (Hostnirvana AutoSSL usually covers this).
  • Use “Full” only if you cannot use “Full (strict)” yet.

Step 6: If you’re using Hostnirvana email, set mail DNS in Cloudflare

Add the mail-related records exactly as Hostnirvana provides:

  • MX records for the domain
  • SPF TXT record
  • DKIM record(s) (TXT or CNAME depending on what’s shown)
  • Optional DMARC TXT record

Cloudflare notes for mail DNS:

  • MX records are not proxyable.
  • Any hostname used for mail (for example, if you create mail.yourdomain.tld) must be DNS only (grey cloud), not proxied.

Step 7: Verify it’s working (after DNS propagation)

You can verify using public DNS lookups (from your computer/server), for example:

dig yourdomain.tld A +short

dig www.yourdomain.tld CNAME +short

dig yourdomain.tld MX +short

dig yourdomain.tld TXT +short

What you’re checking:

  • A/AAAA/CNAME answers match what you set in Cloudflare for the website
  • MX/TXT answers match what Hostnirvana specifies for email/authentication

Should I use Cloudflare with Hostnirvana or not?

Using Cloudflare nameservers instead of Hostnirvana (StackDNS) is usually fine for running Hostnirvana hosting and/or Hostnirvana email, but there are some practical trade-offs on the Hostnirvana side. 

What you don’t get when DNS is not on Hostnirvana (StackDNS)

  • No automatic DNS linking to Hostnirvana services
  • On StackDNS, Hostnirvana can automatically create/maintain the typical records (website, mail, validation records) based on what you enable in the control panel.
  • With Cloudflare nameservers, you must add/maintain those DNS records yourself.
  • More manual work when anything changes
  • If you move a site, change the target IP/hostname, change mail routing, add DKIM, add verification records, etc., you must update DNS in Cloudflare manually.
  • With StackDNS, a lot of this can be “done once” inside Hostnirvana and kept consistent automatically.
  • Some Hostnirvana UI features become “read-only / not applicable”
  • The “DNS management” parts of Hostnirvana aren’t controlling live DNS if your nameservers are not StackDNS.
  • That can make troubleshooting a bit slower because we have to compare what Hostnirvana expects vs what’s actually set at your DNS provider.
  • Higher risk of small DNS mistakes
  • Common examples: missing www record, incorrect MX priority, split/duplicate SPF records, missing DKIM selector record, accidentally proxying a mail-related hostname, etc.
  • These aren’t hard to avoid, but they happen more often when DNS is managed in a separate system.

What is not limited (from the Hostnirvana side)

  • Hostnirvana web hosting still works with external nameservers, as long as A/AAAA/CNAME records point correctly.
  • Hostnirvana email still works with external nameservers, as long as MX/SPF/DKIM/DMARC records are correct.
  • Domain renewal/ownership is separate from where DNS is hosted (nameservers don’t affect renewal).

When I’d recommend using Hostnirvana nameservers instead

  • You want the simplest “set it and forget it” setup, with the most automation inside Hostnirvana.
  • You frequently migrate sites between servers / change hosting targets and want DNS to follow automatically.
  • You want all hosting + DNS changes controlled in one place.