XPROXY

Dynamic DNS (DDNS)

Dynamic DNS (DDNS) lets you use a stable domain name (like myproxy.example.com) to access your XProxy dashboard and proxies — even when your public IP changes.

Configure at: XProxy → General Settings → Dynamic DNS. Supported providers: DNS-O-Matic, Cloudflare, NO-IP, Dynu, DuckDNS.

What is DDNS?

DDNS automatically updates your domain record when your public IP changes. You point your tools to the domain name, and XProxy keeps the IP behind it fresh. This saves time and avoids broken links when the IP rotates or the router restarts.

Why use DDNS with XProxy?

  • One stable domain for your dashboard and all proxy endpoints.
  • No need to remember or update IPs when your ISP changes them.
  • XProxy automatically keeps the domain pointing to your current public IP.
Set up public access first — either Home/NAT Forwarding or VPS Forwarding — before configuring DDNS.

Before you start

  • Your XProxy server is online and can reach the internet.
  • You have an account at one or more DDNS providers you want to use.
  • You know your desired host or domain (for example, yourname.ddns.net or your own domain in Cloudflare).

Quick start

  1. Open XProxy → General Settings → Dynamic DNS.
  2. Select a provider tab.
  3. Toggle Enabled ON.
  4. Fill in the required fields (see provider details below).
  5. Set Update interval to 60 seconds.
  6. Click Save. XProxy syncs immediately.
  7. Click Test to confirm the provider returns "Synchronized".
Dynamic DNS settings page

Provider 1 — DNS-O-Matic

  • Username — your DNS-O-Matic account email/username.
  • Password — your DNS-O-Matic password.
  • Hostname — leave empty to update all.dnsomatic.com, or set a specific host.
DNS-O-Matic configuration

Provider 2 — Cloudflare

  • API Token — token with DNS Read + DNS Edit for the target zone.
  • Zone ID — the zone where your domain lives.
  • Record Name — the DNS A record to update (e.g. proxy.example.com).
  • Proxied — keep OFF for proxy endpoints; ON for public websites/dashboard only.
  • TTL — use 60–120 seconds for faster global updates.
Cloudflare DDNS configuration

Step 1 — Create API Token

Open Cloudflare → My Profile → API Tokens → Create Token. Use the "Edit DNS" template. Scope must include Zone.DNS Read and Zone.DNS Edit. Limit to your target zone. Copy the token.

Create Cloudflare API token
Cloudflare token permissions

Step 2 — Get your Zone ID

Open your domain in Cloudflare → Overview → copy the Zone ID.

Cloudflare Zone ID

Step 3 — Create the A record

Open the DNS tab in Cloudflare and create an A record for your host (e.g. proxy.example.com). Use any IP now — XProxy will keep it updated.

Cloudflare A record

Step 4 — Test and verify

After saving in XProxy, click Test. Then verify from a terminal:

bash
nslookup proxy.example.com
# or
dig +short proxy.example.com

Provider 3 — NO-IP

  • Username and Password/Key — your NO-IP credentials.
  • Hostname — your NO-IP host (e.g. yourname.ddns.net).
NO-IP configuration

Provider 4 — Dynu

  • Hostname — your Dynu host (e.g. yourname.ddnsfree.com).
  • Password — your Dynu account password (hashed automatically).
  • Supports custom domains (point your domain NS to Dynu).
Dynu configuration

Provider 5 — DuckDNS

  • Token — your DuckDNS token.
  • Domain — your DuckDNS subdomain (e.g. yourname.duckdns.org).
  • Note: DuckDNS only supports .duckdns.org subdomains — no custom domains.
DuckDNS configuration

TTL and propagation

TTL (Time To Live) is how long DNS servers cache your record. A shorter TTL means the world learns your new IP faster when it changes.

  • Recommended TTL: 60–120 seconds for proxy use.
  • If using Cloudflare Proxied mode, TTL is managed automatically.
  • Keep Cloudflare Proxied OFF for proxy endpoints — proxied mode routes traffic through Cloudflare, which breaks proxy protocols.

Status indicators

  • Synchronized — provider accepted the update. DNS record matches your current IP.
  • No change — IP is already correct; next update is scheduled.
  • Warning — temporary issue (e.g. rate limit); system will retry automatically.
  • Error — wrong credentials or record not found. Fix the values and test again.
DDNS test result

Troubleshooting

  • Authentication failed — check username, token, or password.
  • Record not found — confirm the host exists in your provider dashboard.
  • Still showing old IP — wait for TTL to expire, or lower TTL for faster updates next time.
  • Service offline — make sure DDNS is enabled in XProxy and you clicked Save.

Tips for best results

  • Set the Update interval to 60 seconds for fast reaction.
  • Trim spaces in fields; only use letters, numbers, and dots in hostnames.
  • Use a shorter TTL (60–120s) for quicker global refresh.
  • If you enable Cloudflare Proxied, note that TTL may be managed automatically.

FAQ

Can I use more than one DDNS provider at the same time?

Yes. Enable multiple providers and XProxy will update them all.

How do I check that my domain points to the new IP?

bash
nslookup your.domain.com
# or
dig +short your.domain.com

What TTL should I use?

Use 60–120 seconds for proxy use. This ensures fast global propagation when your IP changes.

What does "Synchronized" mean?

Your provider confirmed the update. The DNS record now matches your current IP.

My domain still shows the old IP. What should I do?

Give it a bit more time for TTL to pass. Next time, use a shorter TTL like 60–120 seconds. You can also flush DNS cache on your device or router.