LAN

Connect to your server over your local network using its .local mDNS address or direct IP address. This is the fastest connection method, as traffic stays on your LAN and never reaches the Internet.

Use Case

Local connections are the fastest possible, as they do not reach out to the Internet. You must be connected to the same Local Area Network (LAN) as your server.

Watch the Video

Option 1: Local domain

During initial setup, you choose a server name, and your .local domain is derived from it. For example, a server named “My Cool Server” gets the domain my-cool-server.local. This domain uses Multicast DNS (mDNS) to serve as an alias for your server’s LAN IP address. You can change your server name at any time in System Settings.

Tip

The local domain is useful because, by default, your router will sometimes change your server’s IP address on the LAN. If your server’s LAN IP address changes, the local domain will continue to work, even if you move or get a new router!

Option 2: IP Address

Your router automatically assigns your server an IP address on the LAN. The address can be found (1) in your StartOS dashboard at System -> StartOS UI, (2) in your router dashboard, or (3) by pinging your server’s .local domain from the command line of a computer on the same network.

Important

Your router may unexpectedly change your server’s IP address on the LAN. To avoid this, we highly recommend assigning a static IP address. This becomes necessary if you intend to access your server via VPN or clearnet. It also makes the local domain unnecessary. All routers support setting a static IP address for devices on the LAN. Refer to your router’s user manual for detailed instructions.

Private Domains

A private domain is similar to your server’s local domain, except it also works for VPN connectivity, and it can be anything. It can be a real domain you control, a made up domain, or even a domain controlled by someone else.

Similar to your local domain, private domains can only be accessed when connected to the same LAN as your server, either physically or via VPN, and they require trusting your server’s Root CA.

Adding a Private Domain

1. If you haven’t already, assign a static IP address to your server on the LAN. Refer to your router’s user manual for detailed instructions.

2. On the service interface page, click “Add Domain” on the desired gateway table and select “Private Domain”.

3. Enter a fully qualified domain name. It can be anything. For example: domain.com, private.domain.internal, nextcloud.private, nextcloud.fake-tld, or facebook.com.

4. Click “Save”.

5. StartOS will automatically test your DNS configuration. If the test passes, the domain is ready to use. If it fails, a setup modal will appear with instructions to configure your DNS server and the ability to re-test.

DNS for Private Domains

Private domains require your gateway to use StartOS for DNS. StartOS will test this automatically when you add a private domain and guide you through the setup if needed. For more details, see DNS.