Network
Manage your server's connection address, ports, and custom domains.

The Network page is where you control how people reach your server. It shows your connection address, lets you manage ports (allocations), and lets you connect a custom domain. What you see adapts to your application type (a game server versus a web application behind a reverse proxy) and to whether your server has a dedicated or shared IP.
Your Connection Address
At the top of the page, a summary card shows exactly how players connect to your server:
- Connection address: the full address to share. Click it to copy it.
- Connection mode: either Direct connect for most game servers, or Reverse proxy · SSL for web applications, where traffic runs through our proxy and the port is hidden.
- IP type: a Dedicated IP badge if the address belongs to your server alone, or a Shared IP badge if the IP is shared between servers and separated by port.
Below the address, the card breaks the connection down into the IP address, the hostname alias, and either the primary port or, for proxied applications, an SSL indicator handled for you.
Prefer the alias over the raw IP
Whenever possible, share your hostname alias (the DNS address) rather than the raw IP. If the underlying IP ever changes during maintenance or an infrastructure upgrade, the alias keeps working, so you never have to reconfigure your connection settings or notify your players.
Ports & Allocations
An allocation assigns a port to your server. When your server is created, it already has one primary allocation, which is normally used to connect to the server itself.
Primary Allocation
The primary allocation is the default port for your server, marked with a filled star. It drives the connection address shown at the top of the page, and most games reference it automatically in their startup configuration, so you rarely need to edit config files by hand. To change it, click the outlined star on another allocation to set it as primary.
Creating Additional Allocations
Some games or applications need extra ports. For example, Minecraft plugins such as DynMap, PLAN, or Plasmo Voice use additional ports for their web interfaces or for voice chat, and some games use extra ports for RCON or other tasks.
- Open the Network tab for your server.
- Click the Add button. It shows how many allocations you have left (for example, "2 remaining").
- In the dialog, leave the port empty to receive a random available port, or enter a specific one. If a port range is configured, the allowed range is shown.
The number of allocations available depends on your plan. Once no allocations remain, the Add button is disabled.
Notes
Each allocation has a Notes field. Type a short label to remember what a port is used for, and it saves automatically. This helps you avoid accidentally assigning the same port to more than one service.
Removing an Allocation
Click the trash icon on an allocation to remove it. You cannot delete the last remaining allocation.
Some ports are tied to a startup variable for your game or application. These show a Managed by a variable label, and their primary and delete controls are disabled because the game manages them for you.
Domains
Instead of sharing a raw IP address, you can connect a custom domain so players reach your server at a name like play.example.com. The Domains card lists every domain connected to your server, each with a live DNS status indicator:
- Green: DNS is configured correctly and pointing at your server.
- Amber: verification is pending, or DNS is not yet pointing at your server.
- Red: the domain could not be verified. Double-check the domain name and your DNS records.
Use the ⋮ menu on a domain to re-run Verify DNS or to Remove it.
Domain Names Not Included
LBC does not give you a domain name for free. To use a custom domain, you either buy one through the LBC Store, or bring a domain you already own from a registrar such as Cloudflare, Namecheap, or OVH.
Connect a Domain
Click Connect domain to open the dialog. It offers two paths, depending on where your domain lives.
Store domain
For a domain you own through the LBC Store, DNS is created and managed for you automatically:
- Select your domain from the Domain list.
- Optionally enter a subdomain (for example,
play). Leave it empty to use the root domain. - If your server has more than one port, optionally choose which allocation to attach the domain to. It defaults to your primary allocation.
- Click Connect domain. The panel creates the matching DNS record for you. If a conflicting record already exists, enable Update the existing record to overwrite it.
My own domain
For a domain registered elsewhere, you configure DNS at your registrar first, then verify it:
- Enter your domain (for example,
play.example.com). - At your registrar, add the record shown in the dialog: a CNAME record pointing to your alias, or an A record pointing to your IP address.
- Optionally choose which allocation to attach the domain to.
- Click Verify DNS. Once verification succeeds, click Connect domain to finish.
DNS and SSL changes can take a few minutes to apply, and DNS can take up to 48 hours to propagate globally, though it is usually much faster. If verification fails, wait a little and try again.
Once a domain is connected, web applications automatically receive an SSL certificate and become reachable over HTTPS.
Choosing a Registrar
If you don't own a domain yet, you can buy one from any domain registrar. A few popular options:
- Cloudflare: competitive at-cost pricing and excellent DNS management.
- OVH: European provider with good prices and reliable service.
- Namecheap: friendly interface, competitive pricing, free WHOIS privacy.
- Porkbun: low prices, free WHOIS privacy, simple interface.
Domain names usually cost between 10 and 15 USD per year depending on the extension (.com, .net, .gg, and so on). Some extensions such as .xyz or .online can be cheaper, while premium ones like .io can cost more.
Setting DNS Records Manually
When bringing your own domain, these are the records you'll typically add at your registrar.
For a subdomain (CNAME):
| Field | Value |
|---|---|
| Type | CNAME |
| Name | play (or www, app, and so on) |
| Target | Your LBC hostname alias |
| Proxy | DNS only (gray cloud) |
For a root domain (A record):
| Field | Value |
|---|---|
| Type | A |
| Name | @ |
| IPv4 | Your server's IP address |
| Proxy | DNS only (gray cloud) |
If you use Cloudflare, keep the record set to DNS only (gray cloud, not orange). LBC already handles SSL and proxying, so Cloudflare's proxy on top causes conflicts.