How to point a .si domain at Vercel, Netlify, Cloudflare Pages or GitHub Pages

Before you start

The DNS editor in your DomainSpace dashboard supports A, AAAA, CNAME, MX and TXT records. Open the domain, choose DNS records, and enter the name as @ for the root (your-name-here.si itself) or www for a subdomain. Add the domain in your host's dashboard first, because most hosts show you the exact values to enter.

• A root domain cannot hold a CNAME next to other records, so the root uses A records and www uses a CNAME.
• Delete any older A, AAAA or CNAME record at the same name before you add the new one.
• Changes can take time to spread. Netlify's documentation says up to 24 to 48 hours; GitHub's says up to 24 hours. Often it is much faster.
• Hosts issue the HTTPS certificate themselves once DNS points at them.

Vercel

Add the domain under your project's Domains settings. Vercel then shows the values for your project (Vercel: add a domain). External DNS is supported: you only need to change these records, not move the nameservers.

Vercel's knowledge base says 76.76.21.21 is the apex value for most projects, while newer projects can be given a different address from a pool, so use the one in your dashboard (A record and CAA with Vercel). The www target is project-specific too.

Netlify

Add the domain under Domain management for your site. For external DNS, Netlify's documentation lists these records (Netlify: configure external DNS):

Netlify recommends its own DNS for the best result, and says certificates for external DNS may need extra verification steps. If your DNS host supports ALIAS records, Netlify prefers that for the root; ours does not, which is why the A record is used.

Cloudflare Pages

Cloudflare's documentation is specific here (Pages custom domains):

• A subdomain such as `www` can use external DNS. Add it first under Custom domains in your Pages project, then add the CNAME at your DNS host. Adding the CNAME before the domain is set up in Pages can make the site fail with an error.
• The root domain needs the domain to be a Cloudflare zone, meaning its nameservers point to Cloudflare. A plain A record at an external DNS host is not the documented way to serve Pages on a root domain.

For the root domain, use the one-step setup described below: DomainSpace moves your DNS to your own Cloudflare account.

GitHub Pages

Set the custom domain in the repository's Pages settings, then add these records (GitHub: managing a custom domain). The root domain uses four A records, and four AAAA records for IPv6 if you want them:

GitHub recommends verifying the domain in your account settings to prevent others from claiming it, and enforcing HTTPS once available, which it says can take up to 24 hours. If you publish from a branch, a CNAME file in the repository root is created for you.

Our one-step Cloudflare setup

If you want Cloudflare in front of everything, or you need the root domain on Cloudflare Pages, open the domain's DNS page and use Use Cloudflare for DNS. You paste a Cloudflare API token (the page lists the three permissions it needs) or, if you already added the domain in Cloudflare, its two nameservers. DomainSpace copies your A, AAAA, CNAME, MX and TXT records to your Cloudflare account, with the proxy off, and switches the nameservers only after that worked. The token is not stored.

While the domain is on Cloudflare, you edit records in Cloudflare, not in our editor. You can switch back at any time.

Check that it works

After saving, look up the records from your own machine and compare them with what you entered. The answer shows what the internet sees now, which can still be the old value while the change spreads:

dig +short A your-name-here.si
dig +short CNAME www.your-name-here.si

If the old answer keeps appearing, wait and try again; if the host reports the domain as misconfigured, compare each value character by character. For email records on the same domain, see email on a `.si` domain.