> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/configure-private-lan.md).

# Configure a Private LAN

IONOS CLOUD VDC Networking: configure a private LAN in the DCD

[<mark style="color:blue;">DCD</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#dcd) helps you connect the elements of your infrastructure and build a network to set up a functional virtual data center. A LAN is private when no internet access element is connected to it. The quickest way to connect elements is to drag them from the Palette directly onto elements that are already in the Workspace. The DCD will then show you whether and how the elements can be connected automatically.

## Prerequisites

* An existing virtual data center (VDC). See [<mark style="color:blue;">Create a Data Center</mark>](https://docs.ionos.com/cloud/set-up-ionos-cloud/get-started/create-data-center.md).
* At least one server already in the VDC workspace.
* Access to the DCD at [<mark style="color:blue;">https://dcd.ionos.com</mark>](https://dcd.ionos.com).

{% hint style="info" %}
**Note:** <code class="expression">space.vars.ionos\_cloud</code> automatically assigns a `/23` IPv4 CIDR block to every private LAN by default. If you must specify your own CIDR block, use the API instead. For more information, see [<mark style="color:blue;">Specify an IPv4 CIDR Block for a Private LAN</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/specify-ipv4-cidr-block.md).
{% endhint %}

1\. In the **DCD**, go to **Menu** > **Virtual Data Centers**.

2\. Select the data center to configure your elements within it.

![Select a Virtual Data Center (VDC)](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-d6e7c5b1df04c2594dba81c563239b36b5e8fec2%2Fselect-vdc.png?alt=media)

{% hint style="info" %}
**Note:** Select **Create new** if you do not have data centers created. For more information, see [<mark style="color:blue;">Create a Data Center</mark>](https://docs.ionos.com/cloud/set-up-ionos-cloud/get-started/create-data-center.md). Navigate to step 3, after creating a data center.
{% endhint %}

![Create a Virtual Data Center (VDC)](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-37722e179c8af226908a5d8e2e66afb4b03ea328%2Fcreate-vdc.png?alt=media)

3\. Drag a **LAN** element from the **Palette** into the **Workspace**. Rename the LAN if needed by selecting it and updating its name in the **Inspector** pane.

{% hint style="warning" %}
**Warning:** Do not drag the internet access icon onto the LAN. Connecting an internet access element to a LAN converts it from a private LAN to a public LAN, and private IP addresses are reassigned to public IP addresses.
{% endhint %}

4\. Drag the remaining elements from the **Palette** into the **Workspace** and connect them through their [<mark style="color:blue;">NICs</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#nic).

5\. In the **Workspace**, select the required [<mark style="color:blue;">VM</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#vm); the **Inspector** pane will show its properties on the right.

6\. From the **Inspector** pane, open the **Network** tab. Now you can access NIC properties.

7\. Set NIC properties according to the following rules:

* **MAC:** During provisioning, you can specify a custom MAC address. If you do not provide one, a custom address will be automatically assigned. Ensure that any custom MAC address is unicast, adhering to the format `xy:xx:xx:xx:xx:xx`. Here, x represents any hexadecimal digit (0-9, a-f, A-F), and y must be precisely one of 0, 2, 4, 6, 8, A, C, E (or equivalently a, c, e) to conform with unicast addressing requirements.
* **Primary IP:** The primary [<mark style="color:blue;">IP address</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#ip-address) is automatically assigned by the <code class="expression">space.vars.ionos\_cloud</code> DHCP server. You can, however, enter an IP address for manual assignment by selecting one of the reserved IPs from the drop-down menu. Private IP addresses according to [<mark style="color:blue;">RFC 1918</mark>](https://www.rfc-editor.org/info/rfc1918/) must be entered manually.
* **Failover:** If you have an HA setup including a failover configuration on your VMs, you can create and manage IP failover groups that support your HA setup.
* **Firewall:** Configure a firewall.
* **DHCP:** It is often necessary to run a DHCP server in your virtual data center (for example, PXE boot for fast rollout of VMs). If you use your own DHCP server, clear this check box so that your IPs are not reassigned by the <code class="expression">space.vars.ionos\_cloud</code> DHCP server. If DHCP is enabled and the VM's DHCP client requests the interface MTU option, DHCP option 26, the <code class="expression">space.vars.ionos\_cloud</code> DHCP server also sets the largest MTU that the private LAN supports, up to 4074 bytes. For more information, see [<mark style="color:blue;">Configure the MTU for a Private LAN</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/configure-private-lan-mtu.md).
* **Add IP:** To use "floating" or virtual IPs, you can assign additional IPs to a NIC by selecting them from the drop-down list.

8\. Provision your changes.

{% hint style="success" %}
**Note:** The [<mark style="color:blue;">VDC</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#vdc) will create a private network according to set properties.
{% endhint %}

9\. Verify the private LAN configuration:

* Confirm that the LAN appears in the Workspace without an internet access icon attached to it.
* Select the LAN in the Workspace. In the **Inspector** pane, open the **Members** tab and check the **LAN IPv4 CIDR** field for the assigned CIDR block. The field is read-only in the DCD.

## Next steps

* [<mark style="color:blue;">Specify an IPv4 CIDR Block for a Private LAN</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/specify-ipv4-cidr-block.md)
* [<mark style="color:blue;">Add Internet Access</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/add-internet-access.md)
* [<mark style="color:blue;">Merge Private LANs</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/merge-private-lan.md)
* [<mark style="color:blue;">Split a Private LAN</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/split-private-lan.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/configure-private-lan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
