> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/networking/dhcp-static-lease.md).

# Create a DHCP Static Lease

Reserve a fixed IP address for a virtual machine by creating a DHCP static lease entry tied to its MAC address.

A network with the **Dynamic DHCP** option enabled will automatically assign IP addresses to clients. For virtual machines where it's advantageous to ensure the same address is always assigned, you can create a static IP address assigned to the associated MAC address.

**A Static Address can be assigned in one of two ways:**

* **Change a Dynamic Entry to Static**\
  After the VM has already received a DHCP address and currently still holds the lease, designate the address to be static from now on.
* **Create a New Static Entry**\
  Create a new IP address entry, specifying the MAC address from the VM NIC and the desired IP address.

## Change a Dynamic Entry to Static

1. From the Network Dashboard, click **IP Addresses** on the left menu.
2. Find the DHCP address, appearing in the IP Addresses listing as type "Dynamic"
3. Double-click the entry and change the **Type** to ***Static***.
4. Click **Submit** to save the change.

## Create a New Static Entry

1. Obtain the MAC address (within the guest OS or from the VM Dashboard-NICs section.)
2. From the Network Dashboard, click **New** from the left menu.
3. In the **Type** field, select ***Static***.
4. Enter the desired **IP Address**.

{% hint style="warning" %}
**Make sure to assign an IP address that is within the network's address range and not used by another VM on this network.**
{% endhint %}

5. Enter the **MAC Address**.
6. Enter the **Hostname** of the server.
7. Optionally, a **Description** can be entered to record additional administrative information.
8. Click **Submit**.


---

# 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.verge.io/run-the-platform/networking/dhcp-static-lease.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.