Project Zomboid Server Dynamic IP: Update and Test DNS

Dynamic DNS can keep a hostname pointed at a changing home internet address, but it does not create an inbound route or guarantee that the current Project Zomboid client accepts the hostname. This reference walks through the checks that separate those problems: confirm which address changes, keep the server’s local address stable, limit the updater credential, and test from outside your home network. No current-client reconnection test was performed for this guide, so treat the final connection check as something your group must verify.

Confirm the public address changes and can receive inbound traffic#

First, identify the address that players would need to reach. A server computer usually has a private local address on your home network. Your router has a separate internet-facing address, and an external lookup may show the address seen by websites. These values serve different purposes. Dynamic DNS should track the public-facing address for the connection, not the server computer’s private LAN address.

Check the router’s status page and note its WAN or internet IPv4 address privately. Then, from the same home connection, use a reputable external IPv4 lookup and compare the result. Do not publish either full address in a screenshot or support post. If they differ, the router reports a private or shared-range address, or an ISP gateway sits upstream, the router may not own the public route.

Dynamic DNS only changes what address a name resolves to. It does not make unsolicited inbound traffic pass through another router, provider NAT, or a managed network. If the router WAN address and external result do not match, diagnose that boundary before configuring DNS. This Project Zomboid CGNAT guide explains how to compare the clues and ask the provider who controls the upstream layer. A matching address is useful, but still does not prove an outside player can join.

Write down the public address privately at two different times, especially after a router reconnect or provider maintenance, to establish whether it actually changes. Do not create a test outage for your group just to produce a second observation. If your provider assigns a stable address, a dynamic updater may add little value; if the address changes, continue only after you know inbound connections are possible on the service you use.

Keep the server at a stable address inside your home#

The server’s local address should not move around when the router renews device leases. If the server receives a different private address, a router rule may point at the old device address even when DNS correctly points players to your current public address. Keep the local and public parts of the route separate in your notes.

If you administer the router, a DHCP reservation is one common way to ask it to assign the same local address to the server. Router labels and steps vary, so use the manufacturer’s current instructions and avoid changing unrelated firewall or gateway settings. If you already have a working local address and connection rule, record those settings before changing anything. This guide does not reproduce the separate port-forwarding procedure; see the relevant section of the game’s server setup documentation if you still need to configure that path.

After any change, check the server device’s current local address and compare it with the destination your router rule uses. Do not share the address outside your home. If you cannot identify the server’s private address or the rule’s destination, stop and resolve that mismatch first. Updating a public DNS record cannot correct a broken destination inside the house.

Configure the DNS updater with limited access#

Choose a DNS provider and updater that you can maintain. The provider’s current documentation should explain which hostname it can update, how its updater authenticates, and what permissions the credential receives. There is no single control panel or command that applies across DNS providers, operating systems, routers, or updater projects, so follow the instructions for the product you selected rather than copying an unrelated command from a forum post.

Create a dedicated hostname for the server and, if supported, a credential restricted to updating only that record or zone. Do not reuse your main account password, paste a token into a public setup post, or put it in a script or screenshot that others can read. Store it only in the provider’s supported secret field or the updater’s protected configuration. If the service cannot limit what the credential can change, consider whether you are comfortable with that access before enabling it.

Run the updater on a device that stays online when the game server does. A desktop that is shut down overnight cannot report an address change while it is off. A router or always-on device may be an option only if the provider and updater support that exact setup. Check the updater’s own status or logs for an update result, but redact credentials and full addresses before sharing diagnostic output.

Do not infer success because the updater is installed or running. The record itself must resolve to the address currently assigned to your internet connection. Keep a private note of the hostname, the time of the address change, and when the provider reports an update; that timeline can help distinguish an updater delay from a later connection problem.

Check that the hostname resolves to the current public address#

After an update, query the hostname using a DNS lookup tool or provider status page you trust. Compare the answer privately with the public address observed from your home connection. The two should correspond to the current address for the route you intend players to use. A stale result means the client test is premature: inspect the updater’s status, hostname spelling, record type, and provider instructions before asking friends to connect.

DNS providers and caches can take different amounts of time to reflect a change. This guide does not assign a universal TTL or promise a fixed propagation window. Check the record again after the provider’s documented update interval, and use an external resolver if you need to understand what another network currently sees. A provider dashboard showing an update request is not the same as confirming the name resolves as intended from outside your home.

For a controlled comparison, record the local lookup time and the external lookup result without saving or publishing the full address. If answers differ across resolvers, let the provider’s documented caching behavior guide the next check. If the name returns the expected current address but the game client still fails, move on to the client test and diagnosis rather than repeatedly changing DNS settings.

Test hostname entry in the current Project Zomboid client#

The last step is a real attempt from a separate network. A second device on the same home Wi-Fi may use a different route or a local address, so it does not prove that a remote friend can reach the server. Use a compatible PC client on another internet connection, with the same Stable branch, game version, and required mods as the server. Do not test on a public or workplace network unless you have permission to use it for this purpose.

Project Zomboid’s current hostname behavior needs to be checked in the client you actually use. In a 2020 discussion on The Indie Stone forum, a staff reply described manually entering a hostname in a favorite, while an administrator discussed limitations in server-browser announcements. That is historical context from before Build 42, not confirmation of how Stable 42.21 behaves today. The 42.21 Stable release notes document server-browser interface changes but do not establish dynamic DNS or hostname support.

If the current client offers a direct-address field or another supported way to enter a hostname, test that path and record the exact menu or error. Do not assume that a favorite, an announced server listing, and a direct join field behave the same. If the client does not accept the hostname where expected, do not try an old server setting from a forum post as a workaround. Confirm the current instructions with the game’s official documentation or support and keep the result as unverified until the intended client path succeeds.

Record the date, client branch/build, server branch/build, mod list, network used, whether the hostname resolved to the expected address, and the exact outcome. Do not share public addresses, account details, or updater tokens. Only a successful join from that separate network demonstrates that the complete route worked for that configuration at that time; it does not prove future address changes will be handled without another test.

Choose the next step when the test fails#

Use the evidence to decide which layer needs attention. If the hostname resolves to an old address, investigate the updater, DNS record, or caching. If it resolves correctly but the server’s local address changed, review the local reservation and destination. If both appear right but the remote client cannot reach the server, ask the ISP or network owner whether inbound traffic is supported, then review the router and server status. A remote failure can also involve game branch, version, mods, access settings, or client entry behavior; the DNS result alone cannot identify which one.

Keep CGNAT separate from a changing address. A dynamic public address may change over time while still accepting inbound connections. CGNAT can place provider-controlled translation between your router and the internet, where a correct DNS update still cannot open a route. If that is your situation, return to the provider diagnosis above instead of changing the DNS updater again.

If you would rather not operate the server on a household connection, Game Hosting’s Project Zomboid plans move server administration to a managed environment with an integrated panel for settings and restarts. That changes where the server runs; this article does not verify a particular client route, static address, custom hostname, or ISP workaround for a managed plan. Confirm the current service details and test the actual client path before telling your group that a server is ready.

Frequently asked questions#

Does dynamic DNS solve CGNAT?

No. DDNS updates a name-to-address record. It cannot create an inbound route through a provider-operated NAT or another network boundary. Confirm who controls the upstream route before treating the hostname as a solution.

Will the Project Zomboid server browser follow my hostname automatically?

That behavior was not verified for the current Stable client. The dated forum discussion above describes a limitation in server-browser announcements and manual hostname entry in a favorite. Test the exact current client path your players plan to use.

Can friends join using a hostname?

The old staff discussion is not a current compatibility test. Try hostname entry from a compatible external client on the current branch, and record whether that particular path works. Do not promise it to players based only on DNS resolving.

How long should I wait for a DNS change?

There is no universal wait time. Follow your provider’s documentation, check the record from outside your network, and wait until it resolves to the intended current address before running the game-client test.

Quick answers

Does dynamic DNS solve CGNAT?

No. Dynamic DNS updates a name-to-address record; it cannot create an inbound route through carrier-grade NAT. See the separate [CGNAT diagnosis guide](/blog/project-zomboid/project-zomboid-server-cgnat-diagnose-isp-nat/).

Will the Project Zomboid server browser follow my hostname automatically?

Current Stable behavior was not confirmed in this guide. A 2020 staff discussion described manually entering a hostname in a favorite and noted a server-browser limitation; test your current client instead of assuming the old behavior still applies.

Can friends join a Project Zomboid server with a hostname?

A dated 2020 staff reply discussed manually entering a hostname in a favorite, but that is not a test of current Stable. Try the hostname from a compatible client on another network and keep the exact outcome.

How long does a dynamic DNS update take?

It depends on the DNS provider, updater, and caching. Check the hostname against the current public address before asking players to connect; there is no universal wait time established here.