Skip to main content


Configure a DHCP server in a VPC on CoreWeave Cloud

For IP address assignment in a VPC, a DHCP server needs to be deployed. CoreWeave provides a DHCP Server application (dhcpd-server) that supports IP allocation, static assignment and distribution of routes. This is the recommended method for distributing IP addresses inside a VPC, unless a dedicated virtual firewall is used.

In some deployments, users may also choose to distribute VPC IPs from a Windows Domain Controller.


The VPC must be created before the DHCP server is deployed.


To install the DHCP server, navigate to the applications Catalog from the CoreWeave Cloud UI homepage, then find and select the dhcpd-server application:


Selecting the application will expose the configuration options for the DHCP server, shown and detailed below.

Configuration options

SubnetThe VPC subnet where dynamic IP addresses will be assigned
⚠️ Note: This should be the net identifier of the subnet (e.g., for a /24 network, the address would be For a /25 network, either or
Subnet MaskThe netmask of the VPC subnet.
RangeThe range in the subnet to use dynamic IP assignment.
⚠️ Note: This should be formatted as:
<first usable address> <space> <last usable address>
Fixed IP assignment via DHCPA comma-separated list of fixed IP addresses that will bind to the client ID of a Pod or Virtual Server.
RoutesAllows Virtual Servers and Kubernetes Pods to receive specific routes, such as in the case where there is a site to site VPN or virtual firewall deployed.
⚠️ Note: This should be formatted as: <remotenetwork>/<cidr>=<gateway>.
Default gateway to be assigned via DHCPThis will set a default gateway address via DHCP
⚠️ Note: This should not be used if your Virtual Servers and Kubernetes Pods are connected to the regular CoreWeave Cloud Network (CCNN).

Advanced configuration

Advanced configuration for DHCP options are available via the YAML interface, which can be specified within the additionalOptions block. To open the YAML editor, click the YAML tab.

A DHCP YAML manifest

Advanced configurations under the additionalOptions block need to be formatted as a mutli-line literal block, such as:

additionalOptions: |
option first-option x.x.x.x;
option second-option y.y.y.y;
Additional Resources

Learn more about general DHCP configuration options on the ISC website.

VPC and network settings

At the bottom of the application's configuration screen are the Network settings for the DHCP server, in which you can adjust the settings for the server's VPC and network.

Configuration options

VPC NameThe name of your VPC.
⚠️ The VPC must be created before the DHCP service.
Static IP for VPCThe static IP address of the DHCP server (e.g.,

Fixed IP assignment

In order to configure a fixed IP for the Pod or Virtual Server, the client ID of the Pod or Virtual Server must first be set.

By default, some DHCP clients use the hostname, i.e. the Virtual Server name, as the client ID. This makes configuring the DHCP server easy, by allowing you to set a fixed IP for the Virtual Server by name. If this is not the case for your DHCP server, consult the documentation for your DHCP client on how to discover or configure the client ID.


To set the client ID for a Pod, add the following annotation to the manifest: <client-id>

Virtual Servers

The client IDs for Virtual Servers will be the name of the Virtual Server. Otherwise, the client ID can be configured in the DHCP client configuration within the Virtual Server.