Opens in a new tab

Connect a domain to Netlify: the DNS records

Point the root at Netlify’s load balancer — with an ALIAS, ANAME or flattened CNAME to apex-loadbalancer.netlify.com if your DNS host has one, or an A record to 75.2.60.5 if not — and www at your site’s netlify.app name. Remove every AAAA record: Netlify’s load balancer does not serve IPv6.

The records to add

NameTypeValue
@ALIAS / ANAMEapex-loadbalancer.netlify.com
@A (if there is no ALIAS)75.2.60.5
wwwCNAMEyour-site.netlify.app

Use either the ALIAS or the single A record, not both. Sites on Netlify’s High-Performance Edge get different load balancer values, shown in the site’s domain settings. Netlify recommends www (a subdomain) as the primary domain when the DNS stays elsewhere.

IPv6Not with external DNS — remove AAAA records
OrMove the DNS to Netlify DNS, which sets everything itself
CertificateLet’s Encrypt

Check your domain

Enter your domain: we look up its records and compare them with what Netlify expects — the root, www, and any record left over from before.

Step by step

  1. In Netlify, add the domain under Domain management; Netlify adds both the root and www.
  2. At your DNS host, point the root at apex-loadbalancer.netlify.com with an ALIAS or ANAME, or add an A record for 75.2.60.5.
  3. Add a CNAME for www to your-site.netlify.app.
  4. Remove every AAAA record for the root and www, then wait for the certificate.

What to remove

  • All AAAA records: Netlify’s load balancer does not support IPv6.
  • Any other A records on the root — keep only 75.2.60.5 (or the ALIAS).

The certificate

Netlify issues and renews a Let’s Encrypt certificate. It fails while a CAA record excludes Let’s Encrypt, while AAAA or extra A records remain, before the records have propagated — and with DNSSEC turned on when using Netlify DNS, which does not support it.

Common mistakes

  • Leaving AAAA records from the previous host.
  • Adding both an A record and an ALIAS for the root.
  • Delegating www as a separate subdomain.

Sources

Records checked on 26 September 2026 against these official sources:

Know the moment your site stops answering

Add your site and we check it every few minutes, confirm a failure from another location — Europe, North America or Asia — before calling it down, and email you when it stops answering and when it is back. Free for two sites.

Create a free account