Search Engine: Elastic

Article ID: 132285, created on Feb 22, 2018, last review on Feb 22, 2018

  • Applies to:
  • Operations Automation


For the legacy VPS subscriptions, before the upgrade to 7.0, hostnames with the format of vps-$SUB_ID-$ could be resolved correctly, despite the DNS records existed in DNS zone (that belonged to brand).

After the upgrade to 7.0, such DNS records stopped getting resolved.

The DNS server is based on PowerDNS.


The upgrade procedure involved moving the PowerDNS server from 2.x version to 3.x.

PowerDNS (before 3.0) broke strict RFC compatibility by not always checking for the presence of a SOA record first. Since 3.0, RFC compatibility is followed.

Reference: PowerDNS Internals


There is no resolution for such custom behavior.

It is advised to use the native functionality of the Virtualization (Virtuozzo containers) module and configure a single default DNS zone to be used for placing VPS hostname A records.

Setting Up Default Domain

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF