Run a DayZ server at home without a static IP

• With dynamic public IPv4 and correct port forwarding.
• With IPv6 when the router/firewall and player networks support it.
• On a VPS or dedicated server where a public IP is provided.

• 10.0.0.0 - 10.255.255.255
• 172.16.0.0 - 172.31.255.255
• 192.168.0.0 - 192.168.255.255
• 100.64.0.0 - 100.127.255.255

• Public IP: the value returned by api.ipify.org or curl.
• Router WAN IP: the address shown on the router Internet/WAN Status page.
• Local IP and gateway: from ipconfig or PowerShell.
• If the WAN IP is private/100.64.0.0/10 or differs from the public IP, suspect CGNAT or double NAT.

• Does router WAN IP match an external IP checker? If not, suspect CGNAT.
• If public IPv4 exists, check port forwarding and Windows Firewall.
• If no public IPv4 but IPv6 exists, test IPv6 firewall and external IPv6 reachability.
• If neither exists, ask for public IPv4 or use VPS/dedicated hosting.
• If game port works but launcher says blocked, check the query/A2S UDP port separately.

• I want to host a game server from home.
• I need inbound UDP ports to reach my server machine.
• Can I get a public IPv4 address or be removed from CGNAT?
• Normal browsing is not enough; externally initiated UDP traffic must reach me.

• Home: friends, mod tests, learning, low starting cost.
• VPS/dedicated: CGNAT, larger communities, better uptime, stable public IP.
• Home: good when you have public IP, wired network and the machine can stay online.
• Dedicated/bare metal: better for many players, many mods, AI, events and large persistence.

• Server name, password, player limit and camera perspective.
• Time, time acceleration, restarts, basic server messages and logs.
• Central Economy/XML/JSON style settings: loot amounts, spawn points, events and limited mapped static objects.
• Private community server access through password/whitelist style controls.
• Only the files and editors exposed by the provider, not full PC server file control.

• Console pro: easier player access, more uniform client environment, no client-side mod sync issues.
• Console con: no PC Workshop mod loading, no self-hosted server binary, less file and script access.
• PC pro: full modded server environment, Steam Workshop, serverMod/client mod separation, self-hosting/VPS/dedicated hosting options.
• PC con: more ports, keys, performance tuning, mod compatibility and client setup problems.
• On console, a "modded server" often means loot, economy, event, spawn or map object config rather than full client mods.

• One physical host may run many other DayZ or game servers.
• Sharing a CPU with 20-30 other servers makes single-core performance unpredictable.
• Upgrading a package may not improve server FPS if you remain on the same overloaded host.
• More RAM or more slots does not fix weak or oversold CPU.
• Titan Server Launcher keeps ports, mods, updates, logs and probe state under your control.

• External UDP 2302 -> server UDP 2302, player game port.
• External UDP 27016 -> server UDP 27016, Steam/A2S query port.
• External TCP 2305 -> server TCP 2305, only if you use RCon.

• Port Forwarding, Virtual Server, NAT Forwarding or Applications.
• DHCP Reservation, Address Reservation or Static Lease.
• Firewall Rules, IPv6 Firewall or Security.
• UPnP is convenient, but manual rules are better for a real server.
• WAN Status or Internet Status for the router public/WAN IP.

• Game port: UDP 2302 for player connections.
• Query/A2S port: UDP 27016 for server list, launcher and backend checks.
• RCon port: TCP 2305 only when remote RCon administration is used.
• Router port forwarding must target the fixed internal IP.
• Windows Firewall needs inbound rules for the same ports.

• Start menu -> search: Windows Defender Firewall with Advanced Security.
• Left side: Inbound Rules.
• Right side: New Rule.
• Rule Type: Port.
• Protocol: UDP, Specific local ports: 2302,27016.
• Action: Allow the connection.
• Profile: Private and Domain; Public only if your server network profile is Public.
• Name: DayZ Server UDP game and query.
• Create a separate TCP 2305 rule for RCon if needed.

• Game ports: 2302, 2402, 2502, 2602 or similar separated values.
• Query ports: 27016, 27020, 27024, 27028 or other unique UDP ports.
• RCon ports: 2305, 2405, 2505, 2605 only if needed.
• Do not reuse the same query port for two servers.
• Do not open wide ranges unless you have a clear reason.

• HU server: game UDP 2302, query UDP 27016, RCon TCP 2305.
• EU server: game UDP 2402, query UDP 27020, RCon TCP 2405.
• Test server: game UDP 2502, query UDP 27028, RCon TCP 2505.
• Each port needs its own router and Windows Firewall rule.

• Allow inbound connections for DayZServer_x64.exe.
• Inbound UDP 2302 Allow.
• Inbound UDP 27016 Allow.
• Inbound TCP 2305 Allow, only for RCon.

• Do not keep the entire server machine in DMZ.
• Do not expose Windows admin/RDP ports to the internet.
• Use RCon only with a strong password and only when needed.
• Do not publish SteamCMD/Steam credentials, tokens or config passwords.
• Backup and log folders should not be directly web-accessible.

• Separate observed_ipv4 and observed_ipv6 fields.
• Separate IPv4 and IPv6 probe results.
• A failed IPv6 heartbeat should not overwrite a working IPv4 state.
• External blocked should only mean all advertised/tested addresses failed.

• Use wired Ethernet instead of Wi-Fi for the server machine.
• Even small servers need stable upload, not only high download speed.
• Packet loss or unstable ping can cause lag even with good hardware.
• Heavy uploads by other users on the same connection can lag the server.
• Router QoS can help, but it cannot replace a bad upload link.

• CPU: strong single-core performance matters more than many slow cores.
• RAM: 6 GB is the server baseline; 8-16 GB is better for the whole machine.
• Storage: SSD is strongly recommended, M.2 NVMe is better for mods and backups.
• GPU: dedicated GPU is not required because the server does not render graphics.
• Network: wired Ethernet, stable upload, low packet loss.

• AI, bots, dynamic events and mission systems.
• Many vehicles, helicopters, persistent objects and basebuilding items.
• Trader, economy, custom loot and large spawn checks.
• Poorly optimized or very frequent script mods.
• Large modpacks, lots of logs, persistence writes and frequent updates.

• Works on LAN but not externally: CGNAT, port forwarding or Windows Firewall.
• Players can connect but launcher says blocked: query/A2S UDP port is closed or wrong.
• Missing/degraded in Steam list: query timeout, wrong public IP or no A2S response.
• Disappeared after IP change: dynamic IP, DDNS or backend/launcher publish refresh issue.
• API sees IPv6 but IPv4 works: track IPv4 and IPv6 separately.
• Random lag with good CPU: Wi-Fi, packet loss, saturated upload, mod/script load or slow disk.

• The DayZ server process runs locally.
• The server machine has a fixed internal IP.
• Router forwards game and query UDP ports.
• Windows Firewall allows DayZServer_x64.exe and the ports.
• External network receives an A2S/query response.
• Multiple servers use separate ports.

No. Dynamic public IPv4 can work if port forwarding, firewall and IP updates are correct.

Usually not with normal home port forwarding. Ask for public IPv4, use VPS/dedicated hosting, or use a suitable UDP tunnel.

Usually UDP 2302 for game, UDP 27016 for Steam/A2S query, and TCP 2305 for RCon if used. Exact values depend on your config.

Yes. Router forwarding sends traffic to the machine; Windows Firewall inbound rules allow it on the machine.

For reachability problems, use inbound rules first. External players and the API connect into your machine.

Game and query are usually UDP. RCon is usually TCP. Wrong protocol often causes timeouts.

No. A dedicated server does not render graphics. CPU single-core performance, RAM, SSD and network matter more.

The official baseline is 6 GB, but 8 GB for testing and 16 GB or more for normal/modded home servers is better.

Ask for public IPv4, dynamic public IPv4 or CGNAT opt-out, and explain that inbound UDP ports are required for a game server.

Often the game port works but the Steam/A2S query port is closed. The launcher and server list often rely on query response.

Yes, but each server needs unique game, query and RCon ports plus matching router and firewall rules.

Game hosting can be fine for tests, but shared CPU often limits real server FPS. If you have the machine and internet, a self/dedicated setup is clearer and more stable.

Not like a PC server. Console DayZ servers are rented through console server hosting such as Nitrado; the Steam dedicated server is for the PC ecosystem and does not serve Xbox or PlayStation clients.

No. The console client cannot load external Workshop mods, so custom vehicles, armor, weapons, clothing or new client assets do not work. Console customization is mostly limited to XML/JSON/economy/spawn/map-object style server configuration.

No. PC, Xbox and PlayStation are separate server ecosystems. PC players cannot join Xbox or PlayStation servers, and console players cannot join PC servers. DayZ has not had that full cross-platform server model; for practical planning, treat it as something that will not exist and do not build a community or hosting plan around it.