Support
Loading...

Connect a NicNames Domain to Netlify While Keeping DNS at NicNames

18 November 2026

You can use a domain registered at NicNames for a Netlify site without moving its DNS to Netlify. Add the domain to your Netlify site first, then use its external-DNS instructions to point the root domain and www separately. Review existing website and email records before saving any change.

Check where DNS is hosted

Sign in to NicNames and open Domains → ClassicDNS, then the domain’s Settings. Under Name-Servers, Free Name-Servers means the NicNames DNS editor is the relevant place to make this change. If the domain uses custom nameservers, update records at that DNS provider instead. The NicNames WHOIS Lookup and domain lookup guide can help identify the delegated nameservers.

Make a note of the existing root and www website records and any MX or TXT records used by email. A website connection does not require replacing unrelated email records. If you are unsure what an existing record does, ask your website or mail provider before removing it.

Add the domain to Netlify first

In the Netlify site dashboard, open Domain management, choose Add a domain → Add a domain you already own, and enter the domain. Choose External DNS Provider if you want to keep DNS at NicNames. In Production domains, open Pending DNS verification for the custom domain and use the DNS values shown for your site. Netlify may give different values for a High-Performance Edge setup; your account’s instructions take priority over general examples.

Netlify treats the root domain and www as a pair when you assign either one to a site. Plan records for both. For Netlify’s standard network, its documented fallback is a root A record pointing to 75.2.60.5 and a www CNAME pointing to your own {site-name}.netlify.app hostname. Copy the actual www target from your Netlify instructions rather than typing the placeholder. The root A fallback applies where your DNS service does not provide an apex ALIAS, ANAME or flattened CNAME option.

Review and save the NicNames records

  1. On the domain’s NicNames Settings page, open DNS Records → Manage. Review the existing root and www rows before changing them.
  2. For the root, select or add an A row and enter the Netlify-provided IPv4 value in IPv4 address. For www, select or add a CNAME row and enter the Netlify-provided target in Host alias. Use + Add record when a new row is needed, and check the name, TTL and type before saving.
  3. Resolve conflicting old website A, AAAA or www records carefully. An old IPv6 AAAA answer may still send some visitors elsewhere, and a CNAME cannot share its hostname with another ordinary data record. Keep unrelated MX and TXT records. Save the intended DNS change once.

Changing the domain’s nameservers is a separate step and is unnecessary for this external-DNS method. It could interrupt existing email or subdomains if their records are not carried across.

Confirm the website and HTTPS

Return to Netlify’s Production domains and check the domain verification status. Test both the root address and www over HTTPS, then confirm that mail still works. Netlify says DNS changes can take several hours to propagate. If one address fails, compare its public A or CNAME answer with the values in Netlify’s Pending DNS verification panel. Our DNS troubleshooting guide explains how to separate an old cached answer from a wrong authoritative record.

If HTTPS remains pending, check Netlify’s domain and certificate status and look for conflicting old A or AAAA records. A restrictive CAA policy can also prevent certificate issuance; review that policy with your certificate provider before changing it. If the NicNames DNS rows or delegation are unclear, contact NicNames Support with the affected hostname and expected records, without sharing passwords or account tokens.

Share this article:
Ask Jexi