DNS

Netlify DNS record generator

Get Netlify's apex record - ALIAS, ANAME or the fallback A - plus a www CNAME completed with your own Netlify subdomain.

Free, no accountIn your browser

The records below do not change with this, but the page will name your own domain rather than a generic one.

Found on your Netlify site itself - the address it had before you added a custom domain. Needed to complete the www CNAME; Netlify does not publish one fixed target for it.

Try

Result

Apex options ready for your domain

Add one apex record and the www CNAME at the root of your domain.

  • Info

    The apex options below do not need your domain

    Both apex choices Netlify documents are the same fixed target for every site, so there is nothing to fill in to get them right. Typing your domain only makes this page name it instead of speaking generically.

  • Info

    High-Performance Edge sites need different values entirely

    The apex and fallback values below are for standard Netlify hosting only. A site on Netlify's High-Performance Edge uses its own load balancer details instead, which are not published on a general docs page the way the standard ones are.

    Check your Netlify dashboard for a "Pending DNS verification" modal or onboarding PDF before using the fixed values below, if your site is on High-Performance Edge.

  • Info

    The www CNAME needs your own Netlify subdomain

    Netlify's own docs say adding an apex domain automatically adds a www subdomain, but publish no single www CNAME target that applies to every site - that target is your own Netlify subdomain, which only you know.

    Add your Netlify subdomain in the second box above, found on your Netlify site itself as something like your-site.netlify.app.

  • Passed

    Both apex options are ready, pick the one your provider supports

    A CNAME cannot sit at the apex of a domain, so Netlify documents two ways around it: an ALIAS, ANAME or flattening CNAME to the same target, or a plain A record for a provider that supports none of those non-standard types. Netlify's own docs also note that configuring the apex automatically adds a www subdomain, and the other way round, so both records below are meant to be published together rather than either one being optional.

Apex record - ALIAS, ANAME or flattening CNAME

apex-loadbalancer.netlify.com

At @ (ALIAS/ANAME)

Use this if your DNS provider supports ALIAS, ANAME or a flattening CNAME at the apex - leave the host field empty or set it to "@", whichever your provider's panel expects. Do not add the A record below as well.

Apex record - fallback A

75.2.60.5

At @ (A)

Use this only if your DNS provider supports none of ALIAS, ANAME or a flattening CNAME. Do not add the record above as well.

DNS records for your domain

HostTypeValue
@ALIAS/ANAMEapex-loadbalancer.netlify.com
@A (fallback)75.2.60.5
wwwCNAME(add your Netlify subdomain above)

Add only one of the two apex rows, whichever your provider supports. The www row has no real value to copy until your Netlify subdomain is typed in above.

  • Netlify's own docs say adding an apex domain makes it "automatically add a www subdomain" (and the other way round), but do not publish one fixed www CNAME target applicable to every site - this tool says the person's own Netlify subdomain is needed for that record, rather than guessing one.
  • These apex values are for standard Netlify hosting only - a site on High-Performance Edge needs the load balancer details from its own "Pending DNS verification" modal or onboarding PDF in the Netlify dashboard, which this tool cannot see.
  • DNS changes can take up to 24 hours to take effect, per Netlify's own docs; this tool cannot see whether yours have propagated yet - check with the DNS lookup tool next door once they are published.

What this is

This netlify custom domain dns records generator gives you the apex record Netlify documents - an ALIAS, ANAME or flattened CNAME, with a fallback A record for a provider that supports neither - plus the www CNAME completed once you type your own Netlify subdomain.

A CNAME record is not allowed at the apex of a domain, which is the standard problem every static host with a custom-domain apex runs into, Netlify included. Netlify documents two ways around it: an ALIAS, ANAME or flattening CNAME pointed at apex-loadbalancer.netlify.com for a provider that supports one of those non-standard record types, or a fixed A record to 75.2.60.5 for a provider that supports none of them.

For where that apex rule comes from, and how it sits alongside the other records a domain needs, see our blog guide "The DNS records a domain needs, and what each one actually does."

How to read the result

Pick whichever apex record your own DNS provider actually supports - ALIAS, ANAME and flattening CNAME all resolve to the same Netlify target, so there is no reason to prefer one over another beyond which your provider offers. The www CNAME is separate and only appears once you type in your own Netlify subdomain, because Netlify never publishes one fixed target for it the way it does for the apex.

Common mistakes

What goes wrong most often, and how to tell.

  • Adding both the apex A record and the ALIAS/ANAME recordThese are two different answers to the same apex problem, not two records meant to coexist - a provider that supports ALIAS or ANAME should use only that, and the A record fallback is only for a provider that supports neither.
  • Leaving the www CNAME pointed at apex-loadbalancer.netlify.comThat target is documented for the apex record only. The www CNAME needs your own Netlify subdomain, found in your Netlify site itself, not the shared apex load balancer target.
  • Assuming the records take effect the moment they are publishedNetlify's own docs say a DNS change can take up to 24 hours to take effect; a record that looks wrong minutes after publishing may simply not have propagated yet, rather than being wrong.

Questions

What people ask about this tool.

  • A CNAME is not allowed at the apex of a domain by the DNS standard, so a provider that supports ALIAS, ANAME or a flattening CNAME should use the apex-loadbalancer.netlify.com target; a provider that supports none of those falls back to the fixed A record Netlify publishes instead.
  • Netlify assigns every site its own subdomain before a custom domain is ever added - the worked example on Netlify's own page points www at a subdomain like brave-curie-12345.netlify.app, and yours will look the same shape but is unique to your site, so only you can supply it here.
  • Yes, if your DNS provider does not support ALIAS, ANAME or a flattening CNAME at the apex - that is exactly why Netlify documents the fallback A record. Prefer the apex record if your provider supports it; use the A record only when it does not.
  • No. apex-loadbalancer.netlify.com is Netlify's own apex target, documented separately from the www CNAME, which always points at the Netlify subdomain your own site was given before the custom domain was connected.
  • The apex and fallback values on this page are for standard Netlify hosting only. A site on High-Performance Edge uses different load balancer details entirely, shown in its own "Pending DNS verification" modal or onboarding PDF inside the Netlify dashboard - not the fixed values this tool prints.

Sources

Every fixed value here comes from the provider’s own documentation. These pages change, so each says the day it was last read.

Use it from the API

The same check, as one request.

Request
curl -X POST https://resellerhq.com/api/tools/netlify-dns-generator \
  -H "Content-Type: application/json" \
  -d '{"domain":"","netlifySubdomain":""}'
Response
{
  "tool": "netlify-dns-generator",
  "input": {
    "domain": "",
    "netlifySubdomain": ""
  },
  "result": {
    "verdict": {
      "tone": "success",
      "headline": "Apex options ready for your domain",
      "summary": "Add one apex record and the www CNAME at the root of your domain."
    },
    "findings": [
      {
        "id": "domain-not-needed-for-apex",
        "severity": "info",
        "title": "The apex options below do not need your domain",
        "detail": "Both apex choices Netlify documents are the same fixed target for every site, so there is nothing to fill in to get them right. Typing your domain only makes this page name it instead of speaking generically."
      },
      {
        "id": "high-performance-edge-different",
        "severity": "info",
        "title": "High-Performance Edge sites need different values entirely",
        "detail": "The apex and fallback values below are for standard Netlify hosting only. A site on Netlify's High-Performance Edge uses its own load balancer details instead, which are not published on a general docs page the way the standard ones are.",
        "fix": "Check your Netlify dashboard for a \"Pending DNS verification\" modal or onboarding PDF before using the fixed values below, if your site is on High-Performance Edge."
      },
      {
        "id": "netlify-subdomain-needed",
        "severity": "info",
        "title": "The www CNAME needs your own Netlify subdomain",
        "detail": "Netlify's own docs say adding an apex domain automatically adds a www subdomain, but publish no single www CNAME target that applies to every site - that target is your own Netlify subdomain, which only you know.",
        "fix": "Add your Netlify subdomain in the second box above, found on your Netlify site itself as something like your-site.netlify.app."
      },
      {
        "id": "apex-options-ready",
        "severity": "pass",
        "title": "Both apex options are ready, pick the one your provider supports",
        "detail": "A CNAME cannot sit at the apex of a domain, so Netlify documents two ways around it: an ALIAS, ANAME or flattening CNAME to the same target, or a plain A record for a provider that supports none of those non-standard types. Netlify's own docs also note that configuring the apex automatically adds a www subdomain, and the other way round, so both records below are meant to be published together rather than either one being optional."
      }
    ],
    "parts": [
      {
        "kind": "record",
        "title": "Apex record - ALIAS, ANAME or flattening CNAME",
        "value": "apex-loadbalancer.netlify.com",
        "note": "Use this if your DNS provider supports ALIAS, ANAME or a flattening CNAME at the apex - leave the host field empty or set it to \"@\", whichever your provider's panel expects. Do not add the A record below as well.",
        "at": {
          "name": "@",
          "type": "ALIAS/ANAME"
        }
      },
      {
        "kind": "record",
        "title": "Apex record - fallback A",
        "value": "75.2.60.5",
        "note": "Use this only if your DNS provider supports none of ALIAS, ANAME or a flattening CNAME. Do not add the record above as well.",
        "at": {
          "name": "@",
          "type": "A"
        }
      },
      {
        "kind": "table",
        "title": "DNS records for your domain",
        "columns": [
          "Host",
          "Type",
          "Value"
        ],
        "mono": [
          2
        ],
        "rows": [
          [
            "@",
            "ALIAS/ANAME",
            "apex-loadbalancer.netlify.com"
          ],
          [
            "@",
            "A (fallback)",
            "75.2.60.5"
          ],
          [
            "www",
            "CNAME",
            "(add your Netlify subdomain above)"
          ]
        ],
        "note": "Add only one of the two apex rows, whichever your provider supports. The www row has no real value to copy until your Netlify subdomain is typed in above."
      }
    ],
    "limits": [
      "Netlify's own docs say adding an apex domain makes it \"automatically add a www subdomain\" (and the other way round), but do not publish one fixed www CNAME target applicable to every site - this tool says the person's own Netlify subdomain is needed for that record, rather than guessing one.",
      "These apex values are for standard Netlify hosting only - a site on High-Performance Edge needs the load balancer details from its own \"Pending DNS verification\" modal or onboarding PDF in the Netlify dashboard, which this tool cannot see.",
      "DNS changes can take up to 24 hours to take effect, per Netlify's own docs; this tool cannot see whether yours have propagated yet - check with the DNS lookup tool next door once they are published."
    ]
  }
}

Resell the domains these records point at, at your own price, under your own brand.

Get started

Company names and logos are trademarks of their owners, shown only to identify each service.