Can I Use Cloudflare with My Free DigitalPlat Domain? A Complete Setup Guide

Yes, you can use Cloudflare with any free DigitalPlat domain by updating the nameservers in your DigitalPlat dashboard to point to Cloudflare's DNS servers.

The DigitalPlat FreeDomain service is designed to be DNS-agnostic, meaning you can use Cloudflare to manage DNS records for your free .dpdns.org domain (or other supported TLDs) without restrictions. This guide explains the architecture behind this compatibility and provides step-by-step instructions based on the official DigitalPlat/FreeDomain repository.

How DigitalPlat FreeDomain Works with External DNS Providers

DNS-Agnostic Architecture

DigitalPlat FreeDomain handles domain registration and WHOIS management only. According to the source code in documents/tutorial/getting-started/1.2-dns-hosting.md, the platform explicitly states: "DigitalPlat works with any standard DNS provider"【https://github.com/DigitalPlatDev/FreeDomain/blob/main/documents/tutorial/getting-started/1.2-dns-hosting.md#L5-L6】.

The architecture delegates all DNS resolution to external nameservers. When you register a domain, the system stores your chosen nameserver hostnames (NS records) in the registry database, but does not run its own DNS infrastructure. This delegation happens through the dashboard's nameserver configuration interface found in opensource/frontend/domain_view.html【https://github.com/DigitalPlatDev/FreeDomain/blob/main/opensource/frontend/domain_view.html#L48-L55】.

Cloudflare as the Recommended Provider

While DigitalPlat supports any standard DNS host, the official documentation specifically recommends Cloudflare for beginners. The README.md lists Cloudflare as a primary supported provider alongside FreeDNS and Hostry【https://github.com/DigitalPlatDev/FreeDomain/blob/main/README.md#L9】.

Cloudflare's free tier provides DDoS protection, CDN caching, and SSL termination—features that complement DigitalPlat's registration service without requiring any custom integration code in the FreeDomain repository.

Step-by-Step: Configure Cloudflare DNS for Your Free DigitalPlat Domain

Step 1: Add Your Domain to Cloudflare

First, create a Cloudflare account and add your DigitalPlat domain (e.g., example.dpdns.org) to your Cloudflare dashboard. Cloudflare will scan for existing DNS records and provide you with two nameserver hostnames, typically formatted as:

• alice.ns.cloudflare.com
• bob.ns.cloudflare.com

Important: Do not change nameservers in DigitalPlat until you have these exact hostnames from Cloudflare.

Step 2: Update Nameservers in DigitalPlat Dashboard

Log in to your DigitalPlat dashboard and navigate to your domain's Nameservers tab. The interface renders an HTML form defined in opensource/frontend/domain_view.html that submits to /panel/nameserver/update:

<form action="/panel/nameserver/update" method="GET" class="grid gap-4 md:grid-cols-2">
    <input type="text" name="ns1" id="ns1" value="{{ns1}}" required placeholder="NS1" class="input-field">
    <input type="text" name="ns2" id="ns2" value="{{ns2}}" required placeholder="NS2" class="input-field">
    <input type="hidden" name="name" value="{{domain_name}}">
    <button type="submit" class="btn-primary">Update nameservers</button>
</form>

Replace the values in the NS1 and NS2 fields with the Cloudflare nameservers from Step 1, then click Update nameservers.

Step 3: Verify DNS Delegation

After updating (propagation typically takes a few minutes to 48 hours), verify that Cloudflare is authoritative for your domain using dig:

dig NS example.dpdns.org +short

You should see output matching your Cloudflare nameservers:

alice.ns.cloudflare.com.
bob.ns.cloudflare.com.

Once confirmed, you can manage all DNS records (A, CNAME, MX, etc.) directly in the Cloudflare dashboard.

Updating Nameservers via the DigitalPlat API

For automation or bulk management, you can update nameservers programmatically using the same endpoint the web UI uses. The /panel/nameserver/update endpoint accepts GET requests with URL-encoded parameters.

Using cURL

curl -G "https://dash.domain.digitalplat.org/panel/nameserver/update" \
  --data-urlencode "name=example.dpdns.org" \
  --data-urlencode "ns1=alice.ns.cloudflare.com" \
  --data-urlencode "ns2=bob.ns.cloudflare.com"

This request updates the NS records for example.dpdns.org to point to Cloudflare, exactly as the dashboard form does. The backend processes this request and updates the registry database with the new delegation.

Key Files in the FreeDomain Repository

Understanding the source code helps confirm how DigitalPlat handles DNS delegation:

File	Purpose
documents/tutorial/getting-started/1.2-dns-hosting.md	Official documentation stating that "DigitalPlat works with any standard DNS provider" and recommending Cloudflare for beginners【https://github.com/DigitalPlatDev/FreeDomain/blob/main/documents/tutorial/getting-started/1.2-dns-hosting.md#L5-L6】.
README.md	Lists Cloudflare as a supported DNS host alongside other providers【https://github.com/DigitalPlatDev/FreeDomain/blob/main/README.md#L9】.
opensource/frontend/domain_view.html	Contains the HTML form that submits to /panel/nameserver/update, allowing users to input custom Cloudflare nameservers【https://github.com/DigitalPlatDev/FreeDomain/blob/main/opensource/frontend/domain_view.html#L48-L55】.
opensource/whois_server/whois.py	Handles WHOIS queries for domain registration data, confirming the separation between registration services and DNS hosting.

Summary

• DigitalPlat FreeDomain is DNS-agnostic: The platform handles registration only, delegating all DNS resolution to external providers.
• Cloudflare is fully supported: Official documentation in documents/tutorial/getting-started/1.2-dns-hosting.md explicitly recommends Cloudflare as the preferred DNS host for beginners.
• Configuration is straightforward: Update the nameservers in your DigitalPlat dashboard (found in opensource/frontend/domain_view.html) to your Cloudflare-assigned nameservers (e.g., alice.ns.cloudflare.com and bob.ns.cloudflare.com).
• Automation available: Use the /panel/nameserver/update endpoint with curl or similar tools to programmatically update DNS delegation.

Frequently Asked Questions

Is Cloudflare's free tier compatible with DigitalPlat domains?

Yes, Cloudflare's free tier works perfectly with DigitalPlat free domains. The FreeDomain service does not impose any restrictions on which Cloudflare plan you use. Once you delegate DNS to Cloudflare by updating your nameservers in the DigitalPlat dashboard, you gain access to Cloudflare's free DDoS protection, CDN, and SSL features without any additional configuration in the DigitalPlat codebase.

How long does DNS propagation take when switching to Cloudflare?

DNS propagation typically takes between a few minutes and 48 hours when you update nameservers in DigitalPlat to point to Cloudflare. The change is processed immediately in the DigitalPlat backend via the /panel/nameserver/update endpoint, but global DNS resolvers cache the old NS records according to their TTL (Time To Live) values. You can verify the propagation status by running dig NS yourdomain.dpdns.org +short and checking for your Cloudflare nameserver hostnames.

Can I switch back to another DNS provider after using Cloudflare?

Yes, you can switch to any other standard DNS provider at any time. DigitalPlat's DNS-agnostic architecture, as documented in documents/tutorial/getting-started/1.2-dns-hosting.md, allows you to update your nameservers unlimited times through the dashboard or API. Simply replace your current Cloudflare nameservers with the new provider's NS hostnames (e.g., ns1.freedns.org or custom enterprise nameservers) using the same /panel/nameserver/update endpoint.

Does DigitalPlat host its own DNS servers?

No, DigitalPlat does not operate its own DNS servers for free domains. The FreeDomain service focuses exclusively on domain registration and WHOIS management, as implemented in the codebase. DNS resolution is delegated entirely to external providers that you configure in the nameserver settings. This design choice is reflected in the dashboard UI (opensource/frontend/domain_view.html), which provides fields for custom nameserver input rather than offering DigitalPlat-hosted DNS management.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}