Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Virtual Private Cloud
  • Getting started
    • Resource relationships
    • Yandex Cloud network overview
    • Cloud networks and subnets
    • Cloud resource addresses
    • Routing
    • Security groups
    • Gateways
    • Service connections
    • Monitoring network connections
    • Public IP address ranges
    • MTU and MSS
    • DHCP settings
    • Software-accelerated network
    • Quotas and limits
  • DDoS Protection
  • Access management
  • Terraform reference
  • Audit Trails events
  • Release notes
  • FAQ
  1. Concepts
  2. DHCP settings

DHCP settings

Written by
Yandex Cloud
Updated at March 7, 2025

Using DHCP settings, you can configure the same DNS and NTP servers in your subnet used in your corporate network infrastructure which is accessible via a VPN or Yandex Cloud Interconnect. DHCP settings also allow you to assign a domain name or DNS suffix, which will be allowed by the specified DNS server.

You can set the following parameters:

  • DNS domain to search for unqualified names. It is commonly used with the DNS server address to simplify access to resources in an enterprise infrastructure. This option does not affect the name assigned to the VM in Yandex Cloud.
  • DNS server addresses.
  • NTP server addresses.

Changing DHCP settings may prevent VMs from accessing managed database services. To avoid that, you can:

  • In DHCP settings, specify the second address from the dedicated subnet (x.x.x.2) as the default DNS server.
  • Specify the default DNS server address as the DNS forwarder for the *.mdb.yandexcloud.net zone on your network's DNS server.

If you specify DHCP settings for an existing subnet with running Kubernetes virtual machines or nodes, they will apply to these Kubernetes VMs or nodes after you reboot them.

To avoid rebooting the Kubernetes VM and node after changing DHCP settings in the subnet, request a new DHCP lease. To do this, run the following command in the Kubernetes VM or node OS:

sudo netplan apply

Check the settings update. For example, to view the current list of DNS servers, run the following command:

sudo netplan ip leases eth0 | grep -i dns

Was the article helpful?

Previous
MTU and MSS
Next
Software-accelerated network
© 2025 Direct Cursus Technology L.L.C.