Okay, here’s a comprehensive article detailing how to set up Dynamic DNS (DDNS) on Cloudflare, designed to be quick, easy, and thorough, spanning approximately 5000 words:

Set Up Dynamic DNS on Cloudflare (Quick & Easy): A Comprehensive Guide

Introduction: The Need for Dynamic DNS

In the ever-evolving landscape of the internet, static IP addresses are becoming increasingly rare for home users and even some small businesses. Internet Service Providers (ISPs) often assign dynamic IP addresses, which change periodically. This presents a challenge when you want to:

Host a website or server at home: If your IP address changes, your domain name will no longer point to your server, making it inaccessible.
Remotely access your home network: Connecting to devices on your home network (like security cameras, NAS devices, or computers) requires knowing your public IP address. A changing IP breaks this connection.
Run self-hosted applications: Many applications, like game servers, media servers (Plex, Jellyfin), or personal cloud storage (Nextcloud), rely on a consistent IP address for external access.

Dynamic DNS (DDNS) solves this problem. It’s a service that automatically updates your domain name’s DNS records to point to your current, dynamically assigned IP address. Essentially, it gives you a consistent domain name that always points to your home network, even when your IP changes.

Why Cloudflare?

While many DDNS providers exist, Cloudflare offers several compelling advantages:

Free Tier: Cloudflare’s free tier includes DDNS functionality, making it an incredibly cost-effective solution.
Performance and Security: Cloudflare’s global network of servers provides significant performance benefits (CDN caching) and enhanced security (DDoS protection, firewall) to your domain, even on the free plan.
Easy Integration: Cloudflare’s API is well-documented and easy to use, making integration with various DDNS update clients straightforward.
Reputation and Reliability: Cloudflare is a trusted and reputable company with a proven track record of reliability and uptime.
Additional Features: Beyond DDNS, Cloudflare offers a wide range of services, including SSL/TLS encryption, DNS management, and web application firewall (WAF), all within a single platform.

This Guide’s Structure

This guide will walk you through every step of setting up Dynamic DNS on Cloudflare, from creating an account to configuring an update client. We’ll cover various methods and tools to ensure you find the perfect solution for your needs. Here’s a breakdown:

Prerequisites: What you need before you start.
Creating a Cloudflare Account and Adding Your Domain: Step-by-step instructions.
Understanding Cloudflare DNS Records: Essential knowledge for DDNS setup.
Choosing a DDNS Update Client: Exploring different options for various operating systems.
Method 1: Using ddclient (Linux, macOS, and some routers): A powerful and versatile command-line client.
Method 2: Using cloudflare-ddns (Python Script): A cross-platform, Python-based solution.
Method 3: Using Docker and oznu/cloudflare-ddns: A containerized approach for easy deployment.
Method 4: Using Built-in Router Functionality (If Supported): Leveraging your router’s DDNS capabilities.
Method 5: Using Windows Task Scheduler and PowerShell: A native Windows solution.
Testing Your DDNS Setup: Ensuring everything works correctly.
Troubleshooting Common Issues: Addressing potential problems.
Advanced Configuration and Security Considerations: Optimizing your setup.
Conclusion: Wrapping up and next steps.

1. Prerequisites

Before you begin, make sure you have the following:

A Domain Name: You need to own a domain name that you want to use with Dynamic DNS. You can purchase one from various domain registrars (e.g., GoDaddy, Namecheap, Google Domains).
Access to Your Domain Registrar’s DNS Settings: You’ll need to change your domain’s nameservers to point to Cloudflare.
A Device with Internet Access: This could be a computer, server, or router that will run the DDNS update client.
Basic Command-Line Familiarity (for some methods): Some methods require using the command line (terminal or PowerShell). We’ll provide clear instructions, but a basic understanding is helpful.
A Text Editor: You’ll need a text editor to modify configuration files. Notepad (Windows), TextEdit (macOS), or any code editor (VS Code, Sublime Text, etc.) will work.

2. Creating a Cloudflare Account and Adding Your Domain

Create a Cloudflare Account:
- Go to the Cloudflare website: https://www.cloudflare.com/
- Click on “Sign Up.”
- Enter your email address and create a strong password.
- Click “Create Account.”
- You may need to verify your email address.
Add Your Domain:
- Once logged in, you’ll be prompted to add your domain. Enter your domain name (e.g., example.com) without www or any protocol (like http://).
- Click “Add site.”
Select a Plan:
- Choose the “Free” plan for basic DDNS functionality. You can always upgrade later if needed.
- Click “Confirm plan.”
Review DNS Records (Important!):
- Cloudflare will scan your existing DNS records. Carefully review these records. Make sure they are accurate. Cloudflare will import these records, and any errors here will cause problems.
- If you are hosting a website, ensure the A record for your domain (and the www subdomain if you use it) is present and points to your current (soon-to-be-dynamic) IP address. This is crucial for a smooth transition.
- If you are not currently hosting anything, you can safely remove any existing A records for the domain and www. We will be creating a new one later specifically for DDNS.
- Click “Continue.”
Change Your Nameservers:
- Cloudflare will provide you with two nameservers (e.g., dana.ns.cloudflare.com and igor.ns.cloudflare.com). These are unique to your account and domain.
- Go to your domain registrar’s website (where you purchased your domain).
- Find the DNS settings or nameserver management section. The exact location varies depending on the registrar.
- Replace your existing nameservers with the two Cloudflare nameservers. Do not add them as additional nameservers; you must replace the existing ones.
- Save the changes at your registrar.
Complete Setup in Cloudflare:
- Back in Cloudflare, click “Done, check nameservers.”
- Cloudflare will begin checking for the nameserver change. This can take anywhere from a few minutes to 48 hours, although it’s usually much faster (often within an hour). This is due to DNS propagation across the internet.
- You can click “Re-check now” periodically, but be patient.
- You may see a “Quick Start Guide” – you can skip this for now.
Enable DNSSEC (Recommended):
- Once Cloudflare confirms the nameserver change, navigate to the “DNS” tab.
- Scroll down to the “DNSSEC” section.
- Click “Enable DNSSEC.”
- Cloudflare will generate the necessary records. You will need to copy the DS record information provided by Cloudflare and add it to your domain registrar’s DNSSEC settings. This step adds an extra layer of security to your DNS. The exact process for adding the DS record varies by registrar, so consult your registrar’s documentation.

3. Understanding Cloudflare DNS Records

Before we set up the DDNS update client, it’s essential to understand the relevant Cloudflare DNS records:

A Record: This is the most important record for DDNS. It maps a hostname (like home.example.com) to an IPv4 address (like 192.0.2.1). This is the record we’ll be dynamically updating.
AAAA Record: Similar to an A record, but it maps a hostname to an IPv6 address. If your ISP provides IPv6 connectivity, you should also set up a dynamic AAAA record.
CNAME Record: Creates an alias for a hostname. You generally won’t use a CNAME record for the hostname you’re dynamically updating. CNAME records should point to a canonical name (an A or AAAA record), not another CNAME.
Proxy Status (Orange Cloud): This is a crucial Cloudflare feature. When the orange cloud is enabled next to a DNS record, traffic to that hostname goes through Cloudflare’s network, providing performance and security benefits. When it’s disabled (gray cloud), traffic goes directly to your IP address.
- For DDNS, you usually want the orange cloud enabled for the hostname you’re updating. This allows you to take advantage of Cloudflare’s features. However, there are exceptions (see “Advanced Configuration” below).

Creating the A (and AAAA) Record for DDNS

Go to the “DNS” tab in your Cloudflare dashboard.
Click “Add record.”
For an IPv4 address (most common):
- Type: Select A.
- Name: Enter the subdomain you want to use for DDNS (e.g., home, dynamic, or any other name you prefer). If you want to use the root domain (e.g., example.com), enter @.
- IPv4 address: Enter a temporary placeholder IP address. It doesn’t matter what you put here; the DDNS client will update it. You can use 192.0.2.1 or 1.1.1.1.
- Proxy status: Set this to Proxied (orange cloud).
- TTL: Leave this on “Auto.”
- Click “Save.”
For an IPv6 address (if applicable):
- Type: Select AAAA.
- Name: Use the same subdomain you used for the A record (e.g., home).
- IPv6 address: Enter a temporary placeholder IPv6 address (e.g., 2001:db8::1).
- Proxy status: Set this to Proxied (orange cloud).
- TTL: Leave this on “Auto.”
- Click “Save.”

4. Choosing a DDNS Update Client

The DDNS update client is a program or script that runs on your device (computer, server, router) and periodically checks your public IP address. When it detects a change, it sends an update to Cloudflare’s API to modify the A (and AAAA) records.

Here are some popular options:

ddclient: A widely used, Perl-based client available on most Linux distributions, macOS (via Homebrew), and some routers. It’s highly configurable and supports various DDNS providers, including Cloudflare. This is our recommended option for most Linux/macOS users.
cloudflare-ddns (Python Script): A simple, cross-platform Python script specifically designed for Cloudflare. It’s easy to set up and use, making it a good choice for beginners.
Docker (with oznu/cloudflare-ddns): If you’re familiar with Docker, this is a convenient way to deploy a DDNS client in a container. It provides isolation and easy management.
Built-in Router Functionality: Many modern routers have built-in DDNS support. Check your router’s documentation to see if it supports Cloudflare. This is the easiest option if available.
Windows Task Scheduler and PowerShell: For Windows users without Docker, you can create a scheduled task that runs a PowerShell script to update Cloudflare.

We’ll cover each of these methods in detail below. Choose the method that best suits your technical skills and operating system.

5. Method 1: Using ddclient (Linux, macOS)

ddclient is a robust and widely-used DDNS client. Here’s how to install and configure it:

Installation:

Debian/Ubuntu:
bash sudo apt update sudo apt install ddclient
Red Hat/CentOS/Fedora:
bash sudo yum install ddclient # Or dnf install ddclient on newer Fedora versions
macOS (using Homebrew):
bash brew install ddclient
OpenWRT
bash opkg update opkg install ddclient opkg install luci-app-ddns # For web interface integration.

Configuration:

Edit the ddclient configuration file:
- The configuration file is usually located at /etc/ddclient.conf or /usr/local/etc/ddclient.conf. You may need root privileges to edit it.
  bash sudo nano /etc/ddclient.conf
Configure the file with the following settings (replace the placeholders):

“`

Cloudflare DDNS configuration

use=web, web=checkip.dyndns.com/, web-skip=’IP Address’
protocol=cloudflare, \
zone=example.com, \
[email protected], \
password=’your_cloudflare_global_api_key’, \
home.example.com
`` * **use=web**: Tellsddclientto determine your public IP address by querying an external service. * **web=checkip.dyndns.com/, web-skip=’IP Address’**: Specifies the external service to use for IP detection. This is a reliable option. * **protocol=cloudflare**: Specifies that we're using the Cloudflare API. * **zone=example.com**: Replaceexample.comwith your actual domain name. * **[email protected]**: Enter the email address you use for your Cloudflare account. * **password=’your_cloudflare_global_api_key’**: **This is crucial.** You need to use your Cloudflare *Global API Key*, **not** your Cloudflare account password. To find your Global API Key: * Log in to your Cloudflare dashboard. * Click on your profile icon in the top right corner. * Select "My Profile." * Click on the "API Tokens" tab. * Under "API Keys," find "Global API Key" and click "View." * You'll be prompted to enter your Cloudflare password. * Copy the API key and paste it into theddclient.conffile. **Keep this key secret!** * **home.example.com**: Replace this with the *full* hostname you created in Cloudflare (the subdomain and your domain). This is the record thatddclient` will update.
* For IPv6 (optional), add the following below the IPv4 Configuration:

# IPv6 Configuration use=web, web=v6.ident.me/, web-skip='Current IP Address:' protocol=cloudflare, \ zone=example.com, \ [email protected], \ password='your_cloudflare_global_api_key', \ home.example.com
* use=web, web=v6.ident.me/, web-skip='Current IP Address:': Specifies a service for IPv6 address detection.
* Make sure that zone, login, password, and your FQDN is the same.
Edit the ddclient init script (important for systemd):

If your system uses systemd (most modern Linux distributions do), you need to modify the ddclient init script to ensure it runs correctly after a reboot.

```bash
sudo nano /etc/default/ddclient
```

Make sure that the following lines exist and are un-commented:

```
run_daemon="true"
pidfile="/var/run/ddclient.pid"
```
*   If the lines exist but are commented with `#`, remove the `#`.
*    If the file does not exist, you may skip this.

Enable and start the ddclient service:

bash sudo systemctl enable ddclient sudo systemctl start ddclient
* If your system does not use systemd (older systems), use these commands instead:
```
```bash
sudo service ddclient start
sudo update-rc.d ddclient defaults # To enable on boot
```
```
1. Check Status:
  bash sudo systemctl status ddclient # Or sudo service ddclient status

6. Method 2: Using cloudflare-ddns (Python Script)

This method uses a simple Python script, cloudflare-ddns, to update your Cloudflare DNS records.

Prerequisites:

Python 3: Make sure you have Python 3 installed on your system.
requests library: Install the requests library using pip:
bash pip3 install requests

Installation and Configuration:

Download the script:
- You can find the script and instructions on GitHub: https://github.com/K0p1-Git/cloudflare-ddns (This is just one example; there are other similar scripts available. Search for “cloudflare ddns python” on GitHub).
- Clone the repository or download the cloudflare-ddns.py file.
Create a configuration file (config.json):
- Create a file named config.json in the same directory as the script.
- Add the following content, replacing the placeholders:
json { "api_key": "your_cloudflare_global_api_key", "email": "[email protected]", "zone_id": "your_zone_id", "record_name": "home.example.com", "record_type": "A", "proxied": true, "ttl": 1 }
- api_key: Your Cloudflare Global API Key (see instructions in Method 1).
- email: Your Cloudflare account email address.
- zone_id: You need to find your Cloudflare Zone ID. This is a unique identifier for your domain within Cloudflare. To find it:
  - Log in to your Cloudflare dashboard.
  - Select your domain.
  - On the “Overview” page, scroll down to the “API” section.
  - You’ll see “Zone ID” listed there. Copy this ID.
- record_name: The full hostname you want to update (e.g., home.example.com).
- record_type: A for IPv4, AAAA for IPv6.
- proxied: true for proxied (orange cloud), false for DNS-only (gray cloud).
- ttl: Set this to 1 for automatic TTL management by Cloudflare.
- For IPv6, create a separate config.json file (e.g., config6.json) and change "record_type" to "AAAA".
Run the script:

bash python3 cloudflare-ddns.py
* For IPv6: python3 cloudflare-ddns.py -c config6.json
Automate the script (using cron on Linux/macOS):
- To make the script run automatically, you can use a task scheduler like cron.
bash crontab -e
- Add the following line to the crontab file (adjust the path to the script and the interval as needed):
*/5 * * * * /usr/bin/python3 /path/to/cloudflare-ddns.py >/dev/null 2>&1
* This will run the script every 5 minutes. >/dev/null 2>&1 redirects output to prevent emails from being sent.
* For IPv6: Add another line pointing to the IPv6 config:

*/5 * * * * /usr/bin/python3 /path/to/cloudflare-ddns.py -c /path/to/config6.json >/dev/null 2>&1

7. Method 3: Using Docker and oznu/cloudflare-ddns

This method uses Docker to run a pre-built DDNS client in a container. This simplifies deployment and management.

Prerequisites:

Docker: Install Docker on your system. See the official Docker documentation for instructions: https://docs.docker.com/get-docker/

Installation and Configuration:

Create a docker-compose.yml file (recommended):
- Create a new directory for your DDNS project.
- Inside that directory, create a file named docker-compose.yml.
- Add the following content, replacing the placeholders:
“`yaml
version: “3.7”
services:
cloudflare-ddns:
image: oznu/cloudflare-ddns:latest
restart: always
environment:
– API_KEY=your_cloudflare_global_api_key
– ZONE=example.com
– SUBDOMAIN=home
– PROXIED=true
– TTL=1

IPv6 Configuration (optional). Create an additional container.

cloudflare-ddns-ipv6:
image: oznu/cloudflare-ddns:latest
restart: always
environment:
– API_KEY=your_cloudflare_global_api_key
– ZONE=example.com
– SUBDOMAIN=home
– PROXIED=true
– TTL=1
– IPV6=true
“`
- API_KEY: Your Cloudflare Global API Key.
- ZONE: Your domain name (e.g., example.com).
- SUBDOMAIN: The subdomain you want to use (e.g., home). If you want the root domain, leave this blank.
- PROXIED: true or false.
- TTL: Set to 1 for automatic.
- IPV6=true: Set this to true in the second container to enable IPv6 updates.
Run the container:

bash docker-compose up -d
* This will download the oznu/cloudflare-ddns image and start the container in detached mode (-d).
Check the logs:

bash docker-compose logs -f cloudflare-ddns docker-compose logs -f cloudflare-ddns-ipv6 # If you enabled ipv6

Alternatively, you can run the container directly without docker-compose:

“`bash
docker run -d \
–name=cloudflare-ddns \
–restart=always \
-e API_KEY=your_cloudflare_global_api_key \
-e ZONE=example.com \
-e SUBDOMAIN=home \
-e PROXIED=true \
-e TTL=1 \
oznu/cloudflare-ddns:latest

IPv6 (optional):

docker run -d \
–name=cloudflare-ddns-ipv6 \
–restart=always \
-e API_KEY=your_cloudflare_global_api_key \
-e ZONE=example.com \
-e SUBDOMAIN=home \
-e PROXIED=true \
-e TTL=1 \
-e IPV6=true \
oznu/cloudflare-ddns:latest
“`

8. Method 4: Using Built-in Router Functionality (If Supported)

Many routers have built-in DDNS support. This is often the simplest option if your router supports it.

Access your router’s web interface: This usually involves typing your router’s IP address (often 192.168.1.1 or 192.168.0.1) into your web browser. Consult your router’s documentation for the correct address and login credentials.
Find the DDNS settings: The location of these settings varies greatly depending on the router manufacturer and model. Look for sections labeled “Dynamic DNS,” “DDNS,” or similar.
Select Cloudflare as the provider: If your router supports Cloudflare, you’ll likely see it in a list of DDNS providers.
Enter your credentials: You’ll need to enter your Cloudflare account email and your Global API Key (see instructions in Method 1). You may also need to specify your domain name and the subdomain you want to use.
Save the changes and test: The router should automatically update your IP address with Cloudflare.

9. Method 5: Using Windows Task Scheduler and PowerShell

This method is for Windows users who don’t want to use Docker. It uses a PowerShell script and the Windows Task Scheduler.

Create a PowerShell script (e.g., cloudflare-ddns.ps1):
- Create a new text file and rename it to cloudflare-ddns.ps1.
- Paste the following code into the file, replacing the placeholders:
“`powershell

Cloudflare DDNS Update Script

$apiKey = “your_cloudflare_global_api_key”
$zoneId = “your_zone_id”
$recordName = “home.example.com”
$recordType = “A” # Change to “AAAA” for IPv6
$proxied = $true # $true for proxied, $false for DNS-only
$ttl = 1

Get current public IP address (IPv4)

if ($recordType -eq “A”) {
$ip = (Invoke-WebRequest -Uri “https://api.ipify.org”).Content
}

Get current public IP address (IPv6)

elseif ($recordType -eq “AAAA”) {
$ip = (Invoke-WebRequest -Uri “https://api6.ipify.org”).Content
}
else {
Write-Host “Invalid record type. Must be A or AAAA.”
exit 1
}

Get the record ID from Cloudflare

$headers = @{
“Authorization” = “Bearer $apiKey”
“Content-Type” = “application/json”
}
$url = “https://api.cloudflare.com/client/v4/zones/$zoneId/dns_records?name=$recordName&type=$recordType”
$response = Invoke-RestMethod -Uri $url -Headers $headers -Method Get

if ($response.result.Count -gt 0) {
$recordId = $response.result[0].id
```
# Update the DNS record
$body = @{
    "type"    = $recordType
    "name"    = $recordName
    "content" = $ip
    "ttl"     = $ttl
    "proxied" = $proxied
} | ConvertTo-Json
$updateUrl = "https://api.cloudflare.com/client/v4/zones/$zoneId/dns_records/$recordId"
$updateResponse = Invoke-RestMethod -Uri $updateUrl -Headers $headers -Method Put -Body $body

if ($updateResponse.success) {
    Write-Host "Successfully updated DNS record to $ip"
} else {
    Write-Host "Error updating DNS record:"
    Write-Host $updateResponse.errors
}
```
} else {
Write-Host “DNS record not found. Creating…”
$body = @{
“type” = $recordType
“name” = $recordName
“content” = $ip
“ttl” = $ttl
“proxied” = $proxied
} | ConvertTo-Json
```
    $createUrl = "https://api.cloudflare.com/client/v4/zones/$zoneId/dns_records"
    $createResponse = Invoke-RestMethod -Uri $createUrl -Headers $headers -Method Post -Body $body
    if ($createResponse.success)
        {Write-Host "Successfully Created DNS Record $recordName to $ip"}
    else
        {Write-Host "Failed to create Record"}
```
}

“`
* Be sure to change the placeholders at the top with your API Key, Zone ID, record, and type.
Create a scheduled task:
- Open Task Scheduler (search for it in the Windows Start menu).
- Click “Create Basic Task…”
- Name: Give the task a descriptive name (e.g., “Cloudflare DDNS Update”).
- Trigger: Select “When I log on” or “Daily” (and set a specific time). “When I log on” is a good starting point, but you might prefer a regular interval (e.g., every hour) to ensure updates even if you don’t log off frequently.
- Action: Select “Start a program.”
- Program/script: Enter powershell.exe.
- Add arguments (optional): Enter -ExecutionPolicy Bypass -File "C:\path\to\cloudflare-ddns.ps1" (replace C:\path\to\cloudflare-ddns.ps1 with the actual path to your script). The -ExecutionPolicy Bypass argument allows the script to run even if the default PowerShell execution policy restricts it.
- Click “Next” and then “Finish.”
Test the task:
- Right-click on the newly created task in Task Scheduler.
- Select “Run.”
- Check your Cloudflare DNS records to see if the IP address has been updated.

10. Testing Your DDNS Setup

After configuring your DDNS client, it’s crucial to test that it’s working correctly:

Wait for the update interval: Most DDNS clients have an update interval (e.g., 5 minutes, 10 minutes). Wait for this interval to pass.
Check your Cloudflare DNS records:
- Log in to your Cloudflare dashboard.
- Go to the “DNS” tab.
- Verify that the A (and AAAA, if applicable) record for your DDNS hostname has been updated to your current public IP address. You can find your current public IP address by searching “what is my IP” on Google.
Test connectivity from an external network:
- The best way to test is to try accessing your hostname from a device not connected to your home network (e.g., your smartphone using cellular data, a friend’s computer).
- Try pinging your hostname: ping home.example.com (replace with your actual hostname). This should resolve to your current public IP address.
- If you’re hosting a website or service, try accessing it using your DDNS hostname.

11. Troubleshooting Common Issues

Here are some common problems and solutions:

IP address not updating in Cloudflare:
- Check the DDNS client logs: Most clients provide logs that can help diagnose issues. Look for error messages related to API calls or IP detection.
- Verify your API key and Zone ID: Make sure you’re using the correct Global API Key and Zone ID from your Cloudflare account.
- Check your internet connection: Ensure the device running the DDNS client has a stable internet connection.
- Check for firewall issues: Make sure your firewall isn’t blocking the DDNS client from making outbound connections.
- Ensure that you are querying the external IP address: Ensure that the DDNS client is using a method to grab your external IP address and that it’s functioning correctly.
- Test the update client manually: Try running the update client manually (e.g., by restarting the ddclient service or running the Python script) to see if it updates the IP address.
- ddclient specific:
  - Verify /etc/ddclient.conf and /etc/default/ddclient have the correct settings.
  - Check the system logs (/var/log/syslog or similar) for ddclient errors.
Connectivity issues even after IP updates:
- DNS propagation delays: It can take some time for DNS changes to propagate across the internet. Wait a few minutes and try again.
- Firewall rules: If you’re hosting a service, make sure your router’s firewall is configured to forward the necessary ports to your server.
- Incorrect hostname: Double-check that you’re using the correct hostname in your connection attempts.
- Cloudflare Proxy Status: Make sure the orange cloud is enabled for your DDNS hostname (unless you have a specific reason to disable it).
Router DDNS not working:
- Consult your router’s documentation: DDNS configuration varies significantly between router models.
- Check for firmware updates: Update your router’s firmware to the latest version, as this may fix bugs related to DDNS.
- Try a different DDNS provider (temporarily): If your router supports other DDNS providers (e.g., DynDNS), try configuring one of them temporarily to see if the router’s DDNS functionality is working at all.

12. Advanced Configuration and Security Considerations

API Tokens (Recommended over Global API Key):
- For enhanced security, it’s recommended to use Cloudflare API Tokens instead of the Global API Key. API Tokens allow you to grant more granular permissions.
- To create an API Token:
  - Go to your Cloudflare profile (“My Profile” -> “API Tokens”).
  - Click “Create Token.”
  - Choose “Edit zone DNS” template.
  - Under “Zone

Cloudflare DDNS configuration

IPv6 Configuration (optional). Create an additional container.

IPv6 (optional):

Cloudflare DDNS Update Script

Get current public IP address (IPv4)

Get current public IP address (IPv6)

Get the record ID from Cloudflare

Leave a Comment Cancel Reply