Configure DNS in the private network of a dedicated server

You can configure DNS in the private networks of dedicated servers. This allows you to address servers in the private network using domain names instead of IP addresses.

The Private DNS service is used for configuration. The service runs on cloud platform networks, and connection to dedicated server networks is established via the global router.

Private DNS configuration is performed via API; an IAM token for a project is used for request authentication. For a full list of API methods for working with the service, see the Private DNS API.

Configure private DNS in a cloud platform network.
Connect the dedicated server network and the cloud platform network via the global router.
Specify the DNS server IP addresses on dedicated servers.

1. Configure private DNS in a cloud platform network

If you do not already have a private network in the cloud platform, create a private network. The network must be in the same project as the dedicated servers for which you want to use private DNS.
In the Control panel, on the top menu, click Products and select Cloud Servers.
Go to the Private DNS section.
On the DNS Zones tab, click Create DNS zone.
Select a pool.
Enter the zone domain. The domain can contain digits, Latin letters, and hyphens. The domain cannot be a top-level domain, for example example.
Optional: enter the TTL in seconds or leave the default value. TTL is the time that zone resource records are considered up-to-date in the NS server cache and do not require re-caching. The zone TTL will be applied to records that do not have their own TTL specified.
Select a network to add to the zone.
Connect the network to the DNS resolver by checking the network box.
Optional: add records to the zone by clicking Add record and filling in the fields depending on the required record type. You can add, edit, and delete records at any time after creating the zone.
- A or AAAA
- CNAME
- MX
- TXT
10.1. Select the record type — A or AAAA.
10.2. Enter the domain name for which the record will be created. The domain of the zone in which you are creating the record will be added to it automatically.
10.3. Enter the IP addresses to be associated with the domain name: for an A record, IPv4 addresses; for an AAAA record, IPv6 addresses. You can specify a maximum of 100 IP addresses. Enter the addresses separated by a comma or space, or on a new line.
10.4. Enter the record TTL in seconds. To apply the zone TTL, enter -1 or click Use zone TTL.
10.5. Click Add.
10.6. To add another record, click Add record and repeat steps 10.1–10.5.
10.1. Select the record type — CNAME.
10.2. Enter the domain alias — the domain name that should redirect to the target domain. The domain of the zone in which you are creating the record will be added to it automatically.
10.3. Enter the target domain name to which the alias should redirect. This can be any domain name in FQDN format, with a dot at the end.
10.4. Enter the record TTL in seconds. To apply the zone TTL, enter -1 or click Use zone TTL.
10.5. Click Add.
10.6. To add another record, click Add record and repeat steps 10.1–10.5.
10.1. Select the record type — MX.
10.2. Enter the domain name for which the record will be created. The domain of the zone in which you are creating the record will be added to it automatically.
10.3. Enter the priority and mail server name separated by a space, for example 10 mail.example.com. Priority is a number from 0 to 65535; the lower the number, the higher the priority. The mail server name must be in the zone domain.
10.4. Optional: to add another mail server, click + and enter the priority and server name. You can add a maximum of 100 mail servers.
10.5. Enter the record TTL in seconds. To apply the zone TTL, enter -1 or click Use zone TTL.
10.6. Click Add.
10.7. To add another record, click Add record and repeat steps 10.1–10.6.
10.1. Select the record type — TXT.
10.2. Enter the domain name for which the record will be created. The domain of the zone in which you are creating the record will be added to it automatically.
10.3. Enter the record value — any text up to 255 characters.
10.4. Optional: to add another value, click + and enter the record value. You can add a maximum of 100 values.
10.5. Enter the record TTL in seconds. To apply the zone TTL, enter -1 or click Use zone TTL.
10.6. Click Add.
10.7. To add another record, click Add record and repeat steps 10.1–10.6.
Click Create DNS zone.

2. Connect the dedicated server network and the cloud platform network via the global router

Connect the dedicated server network and the cloud platform network via the global router; to do this, use the Connect products and services via global router guide.

3. Specify the DNS server IP addresses on dedicated servers

On each dedicated server in the network that you have connected to the cloud platform network, you need to specify private DNS servers — IP addresses of the DNS resolver from the cloud network.

Ubuntu
Debian
CentOS
Windows

Connect to the server via SSH or via the KVM console.
Open the netplan utility configuration file with the vi text editor:
```
vi /etc/netplan/<netcfg>.yaml
```
Specify <netcfg> — the name of the netplan utility configuration file, for example 50-cloud-init.yaml or 01-netcfg.yaml.
Specify DNS servers for the private network interface that you have connected to the cloud platform network. To do this, add the nameservers block with the DNS resolver IP addresses in the block for the required interface. For example:
```
id1:
  addresses:
    - 192.168.0.3/24
  routes:
    - to: 172.16.0.0/24
      via: 192.168.0.1
  nameservers:
    addresses: 
      - <dns_server_ip_address_1>
      - <dns_server_ip_address_2>
```
Specify <dns_server_ip_address_1> and <dns_server_ip_address_2> — the DNS resolver IP addresses. You can copy the DNS resolver IP addresses in the Control panel: on the top menu, click Products → Cloud Servers → Private DNS → DNS resolvers tab → in the network row, in the DNS resolver field, click .
Press ESC.
Exit the vi text editor with your changes saved:
```
:wq
```
Apply the configuration:
```
netplan apply
```
Optional: reboot the server.