How to connect a .uz domain to Vercel and Netlify: step by step

Vercel and Netlify are the most popular platforms for static sites and projects built with frameworks such as Next.js, Nuxt or Astro. Launching on their .vercel.app or .netlify.app address takes minutes, but a business needs its own domain. Connecting a .uz domain works like any other domain, through DNS records, but there are two approaches and the wrong one can break your email.

Two approaches: add records or change name servers

The first approach keeps DNS where it is and adds the few records the platform asks for. Mail, other subdomains and existing records stay untouched, which is why this is the right choice for most people, especially with company email on the domain. The second approach points the domain's name servers to Vercel or Netlify, which then manage all DNS. In that case you must recreate MX, SPF, DKIM and every other record in the platform's DNS panel, or mail stops the moment the name servers change.

Connecting to Vercel

1. Open Domains in the project settings and add the domain, for example misol-kafe.uz.
2. Vercel shows the required records, usually an A record for the apex and a CNAME for www.
3. Choose the primary address; Vercel can redirect the other one to it.
4. Enter the values in your DNS panel and wait for "Valid Configuration".

Always copy values from your own project, since recommended IPs and CNAME targets change. A domain previously used in another Vercel account may need an extra TXT record to prove ownership. Once records are correct, Vercel issues the certificate automatically. If you later remove the domain from the project, delete the matching DNS records as well, so the name does not keep pointing at a platform that no longer serves it.

Connecting to Netlify

1. Go to Domain management in the site settings and use "Add a domain".
2. For external DNS, Netlify asks for a CNAME from www to your .netlify.app address and an ALIAS, or failing that an A record, for the apex.
3. Verify DNS in the HTTPS section and wait for the certificate.

Most DNS panels for .uz domains have no ALIAS type, so the apex gets an A record to the load balancer IP from Netlify's documentation. Netlify recommends www as the primary address because a CNAME-connected subdomain fully uses its distributed network.

www   IN  CNAME  misol-maktab.netlify.app.
@     IN  A      <load balancer IP from Netlify docs>

When the certificate will not issue

Both platforms use Let's Encrypt. A CAA record allowing only another certificate authority blocks issuance, so add Let's Encrypt or remove the restriction. Leftover records are the other usual cause: an old AAAA record on the apex sends IPv6 users and validators to the old server. Review every old A, AAAA and CNAME on the apex and www before connecting.

dig misol-kafe.uz CAA +short
dig misol-kafe.uz AAAA +short
@     IN  CAA  0 issue "letsencrypt.org"

Example: a school site on Netlify, mail untouched

A private school in Tashkent rebuilt its site in Astro and deployed it to Netlify. Staff rely on company email, so the name servers stayed put. A CNAME for www was added, the apex A record was switched from the old host to Netlify, and a stale AAAA record that still pointed to the previous host was found and removed. The certificate was issued within an hour and mail kept working.

Checking the result

dig www.misol-kafe.uz CNAME +short
dig misol-kafe.uz MX +short
curl -sI https://www.misol-kafe.uz | grep -i server

The response should show server: Vercel or server: Netlify, and MX should be unchanged. If your domain is at sayt.uz, add the records in the cabinet's DNS section; if the platform says "not verified" at first, give caches a little time and check again.