Cloud / DNS platform

How to change DNS records at Cloudflare

Free, fast DNS with an optional proxy/CDN layer. Very common as a DNS host even when the domain is registered elsewhere.

Where the DNS settings live

  1. Sign in to the Cloudflare dashboard.
  2. Choose the domain (Cloudflare calls it a "zone") from the account home.
  3. Click DNS in the left sidebar, then Records.

Adding a record

  1. Click Add record.
  2. Pick the type, then fill in Name (@ for the root) and IPv4 address / Target / Content.
  3. Decide on the orange cloud: Proxied routes traffic through Cloudflare and hides your server IP. DNS only (grey cloud) returns your real value.
  4. Click Save.

Editing or deleting a record

  1. Click Edit on the record row, change the value, and click Save.
  2. Delete is inside the Edit panel, at the bottom left.

Changing the nameservers

  1. Cloudflare DNS only works if the domain's nameservers point at Cloudflare.
  2. Add the site in Cloudflare first and let it import your existing records.
  3. Cloudflare then shows you two assigned nameservers — set those at your registrar.
  4. Activation usually completes within minutes but can take up to 24 hours.

Cloudflare nameservers

These are the values you would set at your registrar to let Cloudflare run your DNS. Always confirm them in your own account — several providers assign per-account values.

  • Two assigned per account, e.g. amy.ns.cloudflare.com

Gotchas at Cloudflare

  • A proxied (orange cloud) record makes the public DNS answer a Cloudflare IP, so external checks will not show your server IP. That is normal.
  • Mail records (MX) must always be grey-clouded — proxying breaks mail.
  • Proxied records force traffic through Cloudflare's SSL settings. "Flexible" SSL with an HTTPS origin causes redirect loops; use "Full (strict)".
  • Cloudflare Registrar does not allow custom nameservers — domains registered there must use Cloudflare DNS.

After you save

DNS changes are not instant. Resolvers keep the old answer until the previous record's TTL expires, so a record with a 4-hour TTL can take 4 hours to change everywhere — occasionally longer if an ISP ignores TTLs. Check what the world currently sees before assuming something is broken, and see the troubleshooting page if it still looks wrong after the TTL has passed.

Other cloud / dns platform guides