ThisCalculator

Everyday

Days to Die Server Not Showing in List: Fixes

Updated · Standard formula, shown below

Days to Die Server Not Showing in List: Fixes

If your DayZ (Days to Die) dedicated server is not appearing in the in-game server list, the cause is almost always a network configuration issue—specifically, the server’s ports are not reachable from the internet, or the game’s server browser is filtering it out. This guide walks you through the complete fixes, from verifying your server is actually running to configuring port forwarding and firewall rules, and finally using the direct-connect workaround.

Background: Why Servers Disappear from the List

DayZ (the standalone game, not the mod) uses a master server list that aggregates publicly advertised servers. When you start a dedicated server, it sends a heartbeat to the master servers, which then include it in the list that players see. If the heartbeat never reaches the master servers, or if the game client’s filters exclude it, the server stays invisible. The most common reasons are:

  • Port forwarding not set up – The server’s query port (default 27016) and game port (default 2302) must be forwarded from your router to the server’s local IP.
  • Windows Firewall or third-party antivirus blocking – Even if the server runs, the OS may block inbound connections, so the heartbeat fails.
  • Client-side filters – The in-game server browser has filters (e.g., “Empty�, “Passworded�, “Modded�) that can hide your server if they don’t match.
  • Steam query port mismatch – If you changed the query port in the server config, the client may not see it unless the port is correctly advertised.

Step 1: Verify the Server is Actually Running and Reachable

Before touching network settings, confirm the server process is up and listening. On the server machine, open a command prompt (Windows) or terminal (Linux) and run:

netstat -an | findstr :2302

You should see a line with LISTENING on port 2302 (or whatever you set in server.cfg). If not, the server failed to start—check the console output for errors. Also verify that the server’s server.cfg contains a valid steamMasterServerConnectToken (a 64-character hex string) and a steamQueryPort (default 27016). Without a valid token, the server cannot register with Steam’s master server list.

Step 2: Configure Port Forwarding Correctly

Port forwarding tells your router to send incoming traffic on specific ports to the server’s local IP. You’ll need to log into your router’s admin panel (usually at 192.168.1.1 or 192.168.0.1) and find the “Port Forwarding� or “Virtual Server� section. Create two rules:

  1. Game port: TCP/UDP, external port 2302, internal port 2302, IP = server’s local IP (e.g., 192.168.1.100).
  2. Query port: UDP, external port 27016, internal port 27016, IP = same server IP.

If you changed the game port in server.cfg, adjust accordingly. Also, if you’re using a dedicated server with SteamCMD, you may need to forward the Steam authentication port (default 8766) as well. After saving, verify the ports are open using an online port checker (e.g., yougetsignal.com) while the server is running.

Step 3: Open Firewall Ports on the Server

Windows Firewall often blocks inbound connections by default. Open “Windows Defender Firewall with Advanced Security� and create two inbound rules:

  1. Allow TCP/UDP on port 2302 (game).
  2. Allow UDP on port 27016 (query).

If you use third-party antivirus with a firewall, add exceptions there too. On Linux, use ufw or iptables to allow these ports. After adding rules, restart the server and test again.

Step 4: Check Client-Side Filters and Direct Connect

Even with perfect network setup, the server browser might hide your server due to filters. In the DayZ launcher, click “Filters� and ensure:

  • “Show empty servers� is checked (if your server is empty).
  • “Show full servers� is checked (if it’s full).
  • “Show passworded servers� is checked (if it has a password).
  • “Show modded servers� is checked (if you run mods).

If you still don’t see it, try direct connect: in the launcher, click “Remote� and enter your_public_ip:2302. If that connects, the server is reachable; the issue is purely the browser listing. If direct connect fails, the port forwarding or firewall is still wrong.

Common Problems and Their Specific Fixes

  • Server shows in LAN but not internet – This means the server is broadcasting on the local network, but the internet-facing ports aren’t forwarded. Double-check your router’s WAN IP (it must be a public IP, not a CGNAT one—see below).
  • Server appears but is “Not Responding� – The query port is likely blocked or the server is overloaded. Ensure UDP 27016 is open and the server has enough CPU/RAM.
  • Server disappears after a few minutes – The heartbeat may be failing due to a temporary network hiccup. Check the server log for “Master server connection lost� errors. Also ensure your public IP hasn’t changed (if it’s dynamic, consider a dynamic DNS service).
  • Port forwarding doesn’t work because of CGNAT – If your ISP uses Carrier-Grade NAT, your router’s WAN IP is not a public IP, and port forwarding won’t work. You’ll need to use a VPN or a VPS to host the server.

Advanced: Using a VPS or VPN for Reliable Listing

If you’re behind CGNAT or your home connection is unreliable, renting a virtual private server (VPS) is the most reliable solution. A VPS gives you a public IP and full control over the firewall. The process is the same as local hosting, but you don’t need port forwarding—just open the ports in the VPS’s firewall (e.g., ufw allow 2302/tcp). This also avoids the issue of dynamic IPs. Alternatively, a VPN service that provides a public IP (like a dedicated IP VPN) can work, but it adds latency and may not be allowed by the VPN’s terms.

Frequently Asked Questions

Why does my server show in the list for me but not for my friends?

If you can see it but your friends can’t, it’s likely because your friends’ game clients are filtering it out (e.g., they have “Show empty servers� unchecked) or their ISP blocks the query port. Have them try direct connect with your public IP. If that works, it’s a filter issue.

Do I need to forward both TCP and UDP?

Yes, the game port (2302) uses both TCP and UDP, while the query port (27016) uses only UDP. Forwarding both TCP and UDP for 2302 is safe and ensures compatibility.

What is the Steam query port and why does it matter?

The Steam query port (default 27016) is used by the master server to ping your server and get its status (player count, map, etc.). If this port is blocked, the master server may still list your server, but it will show as “Not Responding� and eventually be removed.

Can I change the game port to avoid conflicts?

Yes, you can change the game port in server.cfg (e.g., to 2402). If you do, you must update both the port forwarding rule and the direct connect address. The query port can also be changed, but it must be unique per server instance.

My server is on a dynamic IP—will it disappear when the IP changes?

Yes, if your public IP changes, the master server will lose contact. Use a dynamic DNS service (like No-IP) and set up your router to update it. Then, players can connect via the domain name instead of the IP.

Why does the server list show a different version than my server?

This happens when the server and client are on different game versions. Ensure both are updated to the same version. If you’re using a modded server, the mods may also need to match the client’s mod list.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.