How do I set up a DCS World dedicated server?

To set up a DCS World dedicated server, install the modular server build on a 64-bit Windows PC, launch it once, add a .miz mission through the local web interface, and forward port 10308 TCP and UDP to that PC. Allow DCS through Windows Firewall, then test from an external connection.

What do you need before installation?

You need a Windows host with adequate CPU performance, memory and storage for the missions and terrain you plan to run. The dedicated process does not render a cockpit, so its GPU demand is modest, but large missions with many scripted or AI-controlled units can still load the CPU and consume substantial memory.

• Storage: Use an SSD and leave room for the base server, required terrain data, missions, logs and updates.
• Network: A wired connection, stable upload capacity and access to the router are strongly recommended.
• Local address: Reserve a fixed LAN address for the server so port forwarding does not break after a router restart.
• Internet address: Normal public hosting requires a public IPv4 address. Carrier-grade NAT, commonly called CGNAT, prevents ordinary router forwarding.
• DCS account: The server may request DCS account authorisation, but the account does not need to own every hosted aircraft or terrain module.

A separate machine is preferable for a persistent public server. Running the server beside the DCS client on one PC is possible for smaller sessions, but both processes compete for CPU time, memory and storage access.

The dedicated package is separate from the normal Steam or standalone client. Players from either client edition can connect when their DCS builds are compatible; our guide to DCS installation paths, editions and firewall access covers the client-side foundation.

Installing and configuring the dedicated server

The modular installer creates a headless DCS World installation and lets you avoid downloading terrain components you will never host.

1. Reserve the host's LAN address. Configure a DHCP reservation in the router, or assign a suitable static address without creating an address conflict.
2. Download and extract the installer. Our modular dedicated-server package and extraction instructions provide DCS_World_Server_modular.exe. Extract the archive before running the executable rather than launching it from inside the compressed file.
3. Install the required components. Keep the dedicated installation separate from the playable DCS client and select the terrain data required by your missions. Aircraft licences and cockpit files are not needed merely to host aircraft slots.
4. Launch the server once. Run it under the Windows account that will operate it and complete DCS account authorisation if requested. This first run creates the server's configuration, mission and log folders beneath that account's Saved Games directory.
5. Open the local management page. The browser interface normally opens automatically; it is usually available at on the server PC. Set the server name, password if required, player limit and game port.
6. Add a mission. Put the .miz file in the server instance's mission folder, normally under %USERPROFILE%\Saved Games\DCS...\Missions, then add it to the mission list in the web interface. The exact DCS folder suffix varies between installations and named instances.
7. Configure the mission rotation. Add further missions if required and choose the desired order, restart and pause behaviour. The maximum-player setting only limits connections; playable aircraft slots must already exist in each mission.
8. Allow and forward the game port. Permit the server executable through Windows Firewall on the active network profile, then forward the configured game port from the router to the reserved LAN address.
9. Start the mission and test externally. Ask a player outside your home network to connect using the public IPv4 address and game port. A test from the same LAN can fail because some routers do not support NAT loopback, even when external access works.

Which ports does a DCS dedicated server need?

A standard DCS World server uses port 10308 over both TCP and UDP for game traffic unless you change the port in its settings.

The router rule, Windows Firewall rule and port shown in the DCS server settings must agree. If you choose a custom game port or operate several instances, give every instance a unique port and forward each one separately.

Optional services need their own ports and firewall rules. For example, a community using Simple Radio Standalone should configure it separately using our DCS-SRS client and server setup; SRS does not share the DCS game port.

Why can't players see or join the server?

Most connection failures come from an incorrect forwarding target, a missing UDP rule, CGNAT or a firewall rule attached to the wrong Windows network profile.

Clients on the same network should normally connect using the server's LAN address, while internet players use its public address. A mistake we see constantly is testing the public address from inside the same network and treating a router's lack of NAT loopback as proof that the server is closed.

Do you need DCS module licences on the server?

The dedicated server does not need paid aircraft or terrain licences, although the required terrain data must be installed on the server. Each player still needs the terrain licence used by the mission and a licence for any paid aircraft slot they want to occupy.

Mods are different from official modules. If a mission depends on a third-party aircraft, asset or script package, install its required server files in the dedicated instance's Saved Games structure, and make sure clients have matching files where required. Do not copy an entire personal Mods folder to the server; one obsolete dependency can stop a mission loading or trigger integrity-check failures.

Running the server unattended

An unattended DCS server should start under the same Windows user that created its Saved Games instance. A scheduled task can launch it after Windows and networking are ready, but running it as the Local System account often creates or looks for configuration under the wrong user profile.

• Back up the instance: Preserve its Config, Missions, scripts and other customised Saved Games content.
• Keep builds aligned: Stop the server cleanly, apply updates with its own updater and restart it before clients join on the updated build.
• Review the log: Use dcs.log after crashes or failed mission loads rather than repeatedly changing unrelated router settings.
• Secure administration: Keep the web interface private and use a secured remote desktop or private management connection instead of forwarding its administration port publicly.
• Separate multiple instances: Give each server its own Saved Games write folder, game port, management port, mission list and log directory.