---
title: DayZ steamQueryPort explained, and how to tell a scheduled restart from real downtime
description: A DayZ server joins on 2302 but answers the server browser somewhere else, and it restarts every few hours on purpose. Those two facts are behind most false 'server down' reports. Here's how to find and set steamQueryPort, read what the Steam query returns, schedule restarts with messages.xml, and monitor a DayZ server so only unplanned downtime pages you.
canonical: https://watchfor.io/blog/dayz-steam-query-port-and-restarts
---

# DayZ steamQueryPort explained, and how to tell a scheduled restart from real downtime

2026-11-16 · WatchFor Team · Game servers · game-servers, dayz, maintenance

A DayZ server joins on 2302 but answers the server browser somewhere else, and it restarts every few hours on purpose. Those two facts are behind most false 'server down' reports. Here's how to find and set steamQueryPort, read what the Steam query returns, schedule restarts with messages.xml, and monitor a DayZ server so only unplanned downtime pages you.

DayZ servers are restarted on purpose, several times a day. A typical
community server goes down every three or four hours to save, respawn loot
and clear memory, and comes back two minutes later. To a status bot, every
one of those is an outage. To a player who arrived during one, so is the
server's absence from the browser afterwards, because the server answers the
browser on a port nobody wrote down.

This guide fixes both: which port DayZ actually answers queries on and how
to set it, what the query reply tells you, how to make restarts predictable,
and how to monitor a DayZ server so you hear about the crash at 4 a.m. but
not the restart at 4 p.m.

## Two ports: the one players use and the one browsers ask

| Port | Set in | Used by |
| --- | --- | --- |
| Game port, 2302 by default | `-port=2302` on the command line | Players connecting |
| Steam query port | `steamQueryPort` in `serverDZ.cfg` | The in-game server browser, the Steam browser, trackers and monitors |
| BattlEye RCon port | `RConPort` in `BEServer_x64.cfg` | Admin tools |

The game port does **not** answer the Steam query. A status tool pointed at
`your-ip:2302` will report your server offline while it's full.

Bohemia's [server configuration page](https://community.bistudio.com/wiki/DayZ:Server_Configuration)
shows `steamQueryPort` with an example value and a comment that sums up why
it exists: it fixes the server not being visible in the client's server
browser.

```cpp
// serverDZ.cfg
hostname = "My DayZ Server";
maxPlayers = 60;
steamQueryPort = 2303;   // UDP, must be forwarded; pick it, don't leave it to chance
```

What port to pick, and what you'll find on servers you didn't set up:

- **Hosted servers** very often use the **game port + 1**: 2303 for a server
  on 2302. That is what we found on most hosted servers while building our
  probe, with a +10 offset at one host.
- **Unset**, the server chooses a query port on its own, starting around
  27016 according to community reports, and it may not register properly.
  Don't leave it unset.
- **Several servers on one machine** each need their own game port, query
  port and RCon port, with no overlap.

Set `RConPort` explicitly as well; Bohemia gives no default and an unset one
can end up anywhere.

### Check what Steam registered

Steam's public `GetServersAtAddress` API lists every game server at an IP,
with the query address and the game port side by side:

```bash
curl -s "https://api.steampowered.com/ISteamApps/GetServersAtAddress/v1/?addr=203.0.113.10" \
  | jq '.response.servers[] | {addr, gameport, appid}'
# { "addr": "203.0.113.10:2303", "gameport": 2302, "appid": 221100 }
```

`appid` 221100 is DayZ. `addr` is what browsers and monitors must query;
`gameport` is what players join. If your server isn't listed, the server
browser can't show it either: check `steamQueryPort`, the UDP forward and
the server's startup log.

## What the Steam query tells you about a DayZ server

Asking the query port (for example with
[python-a2s](https://github.com/Yepoleb/python-a2s)) returns the server
info. From a busy community PvE server while we wrote this:

```text
map: chernarusplus   players: 119/121   version: 1.30.164289   VAC: on
keywords: battleye,no3rd,external,privHive,shard123ABC,lqs0,etm3.800000,entm4.190000,mod,14:35
```

Useful parts:

- **Players and slots.** Exact, from the info reply.
- **Map.** `chernarusplus`, `enoch` (Livonia), `sakhal` or a community map.
- **Version.** 1.30 is the current release ("Badlands", out since October
  15, 2026). A server still on an older build after an update is one nobody
  can join.
- **Keywords.** Server flags written by the game: `battleye`, `no3rd`
  (first person only), `privHive` (private hive), `mod` when mods are loaded,
  and the in-game time at the end (`14:35`).
- **Player names.** Usually empty. DayZ servers return the player list with
  blank names, so judge population by the count, never by names.

## Restarts: make them boring and predictable

Restarts are part of running DayZ, so the goal is that they're **planned,
announced, short and recognisable**.

**Schedule them in one place.** Use either your host panel's scheduler or the
server's `messages.xml`, not both. `messages.xml` can repeat messages,
count down before a shutdown and stop the server when the countdown ends,
with warnings at 90, 60, 45, 30, 20, 15, 10, 5, 2 and 1 minutes, as
Bohemia's [server messages page](https://community.bistudio.com/wiki/DayZ:Server_Messages)
describes. Your process manager (or the host) then starts it again.

```xml
<!-- messages.xml: restart every 4 hours with a countdown -->
<messages>
  <message>
    <deadline>240</deadline>
    <shutdown>1</shutdown>
    <text>Server restart in #tmin minutes</text>
  </message>
</messages>
```

**Keep the schedule fixed.** 00:00, 04:00, 08:00… in one time zone,
published on your Discord and status page. Players plan around fixed times;
they don't plan around "every four hours since the last crash".

**Measure how long a restart takes.** A two-minute restart that becomes a
nine-minute one after a mod update is a problem worth seeing. Mods that
download or validate on start are the usual cause.

## Telling a restart from real downtime

From outside, every restart looks like an outage: the query port goes
silent, then answers again. What separates them is **when** it happens and
**how long** it lasts:

| Signal | Scheduled restart | Real downtime |
| --- | --- | --- |
| Time | Matches your schedule | Any time |
| Duration | Your usual 1–5 minutes | Until someone notices |
| Before | Countdown messages in-game | Nothing, or lag first |
| After | Same version, players return | Sometimes a new version, a wipe, or a changed port |

A monitor can't read your mind, but it can read your schedule. Put the
restart times into recurring **maintenance windows** and you get exactly the
split you want: alerts during windows are held back, outages outside them
are real and get confirmed and sent, and the history still shows each
restart's length.

Two refinements:

- Make each window a little longer than the restart itself (say 10 minutes
  for a 3-minute restart), so a slow start doesn't spill over.
- Keep the confirmation step. Outside a window, a single missed reply
  shouldn't page anyone; a few in a row, or several locations agreeing,
  should.

## Monitoring a DayZ server with WatchFor

A WatchFor **Game server** monitor with the **DayZ** preset queries your
Steam query port over UDP, from the regions you pick. It pre-fills the game
port + 1, and when you add the monitor the **Test** button asks the
address once and, if it's silent, tries the ports DayZ servers commonly use
and offers the one that answered.

![WatchFor game server monitor for a DayZ PvE server: players out of the slots, Chernarus as the map, the game version, VAC and the latency.](/marketing/game/dayz.webp)

Every check records players out of slots, the map, version, VAC and
password state, and the latency from each location, so the monitor page
shows population, busy hours (the honest answer to when restarts hurt
least) and version changes over time.

- **Restarts stay quiet** with recurring
  [maintenance windows](/docs/monitors/maintenance) for your schedule.
- **Outages are confirmed** before an incident opens: the check is repeated,
  from the monitor's other locations when it has several (how many depends
  on your plan).
- **Discord alerts without a bot**, through a channel webhook, with the
  server's last player count and map; a "Back online" message follows.
  Slack, Telegram, Teams and email work the same way.
- **Opt-in rules** for a server that suddenly has a password, loses VAC, or
  sits full or empty.
- **A status page** with players, map and a **Connect** button that opens
  DayZ through Steam on the right game port.

It doesn't use BattlEye RCon or CFTools and can't change anything on the
server; admin tools manage the server from inside, WatchFor checks it from
outside. Game server monitoring is part of the paid plans from Starter,
counted toward the plan's normal monitor total ([pricing](/pricing)). The
[DayZ page](/game-server-monitoring/dayz) has the port table.

## Checklist

1. Set `steamQueryPort` in serverDZ.cfg; game port + 1 is the common choice.
2. Forward it over UDP, along with the game port.
3. Confirm with `GetServersAtAddress` that Steam registered it.
4. Schedule restarts in one place, at fixed times, with a countdown.
5. Give your monitor the same schedule as maintenance windows.
6. Judge population by the player count; names are blank on DayZ.

## Frequently asked questions

### What is the DayZ steamQueryPort?

It is the UDP port the server answers Steam server queries on, set with `steamQueryPort` in serverDZ.cfg. It is separate from the game port (`-port=2302`). Bohemia's own example sets it to 2305; hosted servers commonly use the game port + 1 (2303). If you don't set it, the server picks a port itself and may not show up in the browser, so set it explicitly.

### Why is my DayZ server not showing in the server browser?

Usually the query port: it isn't set, isn't forwarded over UDP, or a status tool is asking 2302 instead. Set `steamQueryPort` in serverDZ.cfg, open it for UDP, restart, and check Steam's `GetServersAtAddress` API for your IP: it shows the query address Steam registered and the game port next to it.

### How do I schedule DayZ server restarts?

Either your host's panel scheduler or the server's own messages.xml, which can repeat messages, count down before a shutdown and stop the server when the countdown ends; your process manager then starts it again. Bohemia's server messages page documents the format.

### Will a monitor alert me every time the DayZ server restarts?

Not if it knows the schedule. Put your restart times in a recurring maintenance window and alerts stay quiet for them, while the check history still shows how long each restart took. Outside the windows, a confirmed outage still alerts.

### Can I monitor a console DayZ server?

Only if it answers the Steam server query from the internet, which PC servers do. Console servers rented through Nitrado are reached differently, and tools that track them often read Nitrado's API instead; don't assume a Steam query will work for them.

---

Canonical page: https://watchfor.io/blog/dayz-steam-query-port-and-restarts · All articles: https://watchfor.io/blog/all.md · Site guide: https://watchfor.io/llms.txt
