Palworld Server Dynamic DNS: Keep One Address Updated

Palworld server dynamic DNS keeps a hostname pointed at your latest public IP, so you do not have to replace the address in your group chat every time your ISP changes it. The important catch: Pocketpair’s current client guide tells players to enter an IP address and port; it does not say whether a hostname works there. Set up DNS, then test name:8211 in the actual client before promising friends they can join that way. Xbox and PS5 use a different route through the Community server list.

Understand what dynamic DNS changes#

Dynamic DNS (DDNS) updates a DNS record when your internet provider gives your router a new public IP. Your friends keep the same hostname; the record behind it changes. The updater usually runs on the router or another device that stays online, checks the current public address, and sends a change to the DNS provider.

For Palworld, the default game port is UDP 8211. DNS does not include a port, so a client that accepts hostnames would still need the configured port, such as your-name.example:8211. If you changed the server’s listening port, use that value instead. Pocketpair’s requirements page documents the default and the need for router forwarding on a home server.

A new hostname only fixes the “which IP should I type?” part. It does not open the router, add a Windows Firewall rule, bypass carrier-grade NAT (CGNAT), or keep a PC awake. Follow the home-router forwarding steps first; if your provider does not give you a reachable public address, see the CGNAT options when that guide is published. For a broader comparison of ways to run the server, start with the Palworld dedicated-server overview.

Compare DuckDNS, No-IP, and Cloudflare updates#

Pick a provider based on whether you need a free subdomain or your own domain, and where its updater can run. These services update DNS records; none makes the Palworld server itself public.

Option	What you manage	How the IP updates	Watch for
DuckDNS	A free duckdns.org subdomain	Official client, compatible router, or HTTPS update request	Protect the update token; keep the updater running
No-IP	A free No-IP hostname or paid domain	No-IP update client or a compatible router	Free hostnames need periodic confirmation; the current FAQ says every 30 days
Cloudflare	A domain you own and a DNS zone	ddclient or a script using Cloudflare’s DNS API	Use DNS-only for ordinary Palworld UDP traffic; a proxied record is not a UDP game tunnel

DuckDNS documents a simple HTTPS endpoint and router/client examples. No-IP’s update-client FAQ says its updater checks for address changes every five minutes; its free-hostname FAQ says confirmation is required every 30 days. Cloudflare’s dynamic-IP guide documents an API or ddclient approach for dynamic IPs. Those details can change, so follow each provider’s current setup page rather than copying a stale router screenshot.

Set up Palworld server dynamic DNS with DuckDNS#

DuckDNS is the shortest route if a free subdomain is enough. Create a DuckDNS account, choose a subdomain, and save its token in a password manager. Do not paste the token in Discord, a public config file, or a screenshot: anyone who gets it could change the DNS record.

1. Choose the device that will run the updater

   Use the router if it supports DuckDNS or a compatible custom provider. Otherwise install DuckDNS’s official updater on the server PC, or run a small scheduled task on another device that stays online. A laptop that sleeps will leave the record stale while it is away.

2. Send an update and check the response

   DuckDNS’s API specification accepts an HTTPS request with your subdomain and token. Keep the token in an environment variable instead of writing it into the command itself:

   $domain = 'your-subdomain'
   $uri = "https://www.duckdns.org/update?domains=$domain&token=$env:DUCKDNS_TOKEN"
   Invoke-RestMethod -Uri $uri

   A successful update returns OK. DuckDNS can detect the current IPv4 address when you omit the optional ip parameter. Its installation page shows official client and router examples. If the response is not OK, check the subdomain and token in the provider dashboard; do not keep retrying a token you may have exposed.

3. Confirm the hostname resolves

   Look up the hostname and compare the returned address with your current public IPv4 address:

   Resolve-DnsName your-subdomain.duckdns.org -Type A

   A record that still shows the old IP means the updater did not run, the wrong subdomain was entered, or a resolver still has a cached answer. Wait briefly and check again before sending the name to the group.

The DNS check proves only that the hostname maps to an address. It does not prove that Palworld accepts the hostname or that UDP 8211 can reach your server from outside the home network.

Use No-IP or your own Cloudflare domain#

No-IP works similarly: create a hostname, install its official update client on an always-on device, then confirm the record in No-IP’s dashboard. If you use the free hostname, schedule the required confirmation every 30 days so it does not expire. A router with a No-IP updater can replace the desktop client, but check the exact service name and credentials your router expects.

With Cloudflare, you need a domain in a Cloudflare DNS zone and a client or script that detects public-IP changes and updates its A record through the API. Cloudflare’s guide lists ddclient as one option. Give an API token only the DNS permissions and zone scope it needs, keep it outside a public repository, and set the record to DNS only. The orange-cloud proxy handles supported web traffic; it does not proxy a normal Palworld UDP game connection. Cloudflare’s own proxy use-case guidance identifies game servers as a non-HTTP use case that needs an applicable Spectrum setup if proxied.

Whichever provider you choose, test the updater after a router restart or a manual IP change that you control. Do not force an IP change on a live game night. The success check is that the DNS record updates to your current public address; the game-client test comes next.

Test the hostname in Palworld before sharing it#

Pocketpair’s current direct-connect guide says to enter an IP address and port below the server list. It does not document hostname support. Provider tutorials disagree, so treat hostname:8211 as something to verify on your own client rather than an official guarantee.

1. Keep the server running and confirm the DNS A record points to its current public IP.
2. On a PC that uses the direct-connect field, open Join Multiplayer Game (Dedicated Server) and try your-hostname:8211. If you changed the listening port, substitute that port.
3. Repeat from another internet connection, such as a friend’s connection or a phone hotspot. A test from inside the same home network can pass or fail because of router loopback behavior and does not prove outside access.
4. Use the public IP with the same port as a control. If IP works but the hostname does not, investigate client hostname handling or DNS caching. If neither works, troubleshoot forwarding, firewall, server state, or CGNAT; changing DNS alone will not fix those layers.

Give Xbox and PS5 friends the Community server route#

Xbox and PS5 players do not join by typing your DDNS hostname into the direct-connect field. Pocketpair says those clients need the server deployed as a Community server, then the player selects Community server and finds it in the in-game list. That route depends on the server being configured and visible there; having a correct DNS record does not register it or make it easier to search.

Use a distinct server name and tell console friends the words to search for. If the listing is private, full, filtered, or slow to appear, a DNS update will not fix that. For clients with a dedicated-server address field, Pocketpair documents an IP and port but does not mention DNS names; test hostname entry with the exact client version before relying on it. A community listing and a DDNS hostname solve different parts of the connection problem.

Check DNS, ports, and reachability separately#

When friends still cannot join, test one layer at a time. First resolve the hostname and compare it with your current public IP. Next confirm that the server is running and listening on its configured UDP port. Then verify that the router forwards that same UDP port to the server PC and the operating system firewall allows it. Do the final connection check from outside the home network.

If DNS shows an old address, check that the updater runs on the router or an always-on device and that its account token is current. If DNS is correct but neither the hostname nor IP works, revisit forwarding and firewall rules. If the router’s WAN address is not publicly reachable, ask the ISP whether you are behind CGNAT or use the separate no-forwarding options in B13 once published. Do not open RCON or REST API ports to solve a game-port problem.

The practical rule is simple: DDNS gives your group a name that can follow address changes; only a current client test tells you whether that name works in Palworld’s direct-connect field. For console players, share the Community server name instead.

Quick answers

Can you join a Palworld server with a domain name instead of an IP?

Pocketpair’s current guide documents an IP address and port, not hostname support. Test hostname:port in your own client before you share it as a working address.

How do I stop my Palworld server IP from changing?

Use a dynamic DNS updater on your router or an always-on device to point a hostname at the latest public IP.

Does DuckDNS work with Palworld?

DuckDNS can keep a hostname pointed at your current IP, but Pocketpair does not document whether Palworld’s direct-connect field accepts hostnames.

Can Xbox or PS5 players join with a dynamic DNS name?

Pocketpair directs Xbox and PS5 players to the Community server list; a DDNS record does not create or publish that listing.