Skip to content
Cloudflare Docs

Manage DNS records

Consider the sections below for step-by-step instructions on managing DNS records at Cloudflare.

To better understand what DNS records are, refer to Overview. For context around common records you want to review when getting started at Cloudflare, refer to review DNS records.


Basic operations

Create DNS records

To create a DNS record in the dashboard:

  1. In the Cloudflare dashboard, go to the DNS Records page.

    Go to Records
  2. Select Add record.

  3. Choose a record Type.

  4. Complete the required fields, which vary per record. Particularly important fields (for some records) include:

    • Proxy status: For A, AAAA, and CNAME records, decide whether hostname traffic is proxied through Cloudflare.
    • TTL: Short for Time to Live, this field controls how long each record is valid and — as a result — how long it takes for record updates to reach your end users.
    • Comment and Tag: Record attributes meant for your reference.
  5. Select Save.

Edit DNS records

To edit DNS records in the dashboard:

  1. In the Cloudflare dashboard, go to the DNS Records page.

    Go to Records
  2. On a specific record, select Edit.

  3. Make any necessary changes.

  4. Select Save.

Delete DNS records

To delete DNS records in the dashboard:

  1. In the Cloudflare dashboard, go to the DNS Records page.

    Go to Records
  2. On a specific record, select Edit.

  3. Select Delete.

  4. Select Delete again to confirm.


Use cases

Update an origin IP address

If your hosting provider changes or your origin IP address changes, update the Content value of the relevant DNS records (usually A or AAAA records).

If you are not sure which IP address to use, refer to your hosting provider's documentation.

Originless setups

If you need a placeholder address for an originless setup (also referred to as parked domain or redirect-only), you can use the reserved IPv6 address 100:: or the reserved IPv4 address 192.0.2.0 in a proxied DNS record.

This allows you to route requests using products such as Redirect Rules, Page Rules, or Workers.


Further guidance