DayZ networking uses several related UDP ports. On Chapter22 managed hosting, allocations are published for you — DIY readers must open them explicitly.
Port table
| Service | Port | Protocol | Public? |
|---|---|---|---|
| Game | 2302/UDP (default; or panel allocation) | UDP | Yes |
| Steam query | Often 27016/UDP (steamQueryPort) | UDP | Yes for launcher list |
| BattlEye | Relative to game (often game+2) | UDP | Yes |
| RCon | Often 2305/UDP (varies) | UDP | Prefer private |
Managed hosting (Chapter22)
- Open the DayZ server in Pterodactyl.
- Copy allocated game/query ports.
- Keep
serverDZ.cfg/ BattlEye config aligned with those ports. - For launcher visibility, query + BattlEye must be reachable.
This page is the canonical ports hub. The older thin article Which DayZ Ports Should Be Public should point readers here.
DIY / self-hosted readers
DIY VPS: allow game + query + BattlEye UDP in OS firewall and provider SG. See Linux ports. Keep RCon off the open internet when possible.
Related
- Deepen visibility issues in Server Not Showing in Launcher.
- RCon hardening: Safe Defaults.
Related guides
- Server Not Showing in Launcher
- Which DayZ Ports Should Be Public
- RCon Safe Defaults
- How to Open Ports on a Linux VPS (UFW, firewalld, iptables)
- VPS Port Forwarding Explained (Firewall vs Home Router)
- DDoS Protection Basics for Game Servers
Frequently Asked Questions
Default game port?
2302/UDP is the common default; panels may remap — use your allocation.
Steam query?
Often steamQueryPort around 27016/UDP — must match serverDZ.cfg.
Should RCon be public?
Prefer private/allowlisted. CFTools should use tight credentials.
Need help?
If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.
Build the server. Grow the community. Start your next chapter.