Article ID: 118200, created on Oct 24, 2013, last review on May 11, 2014

  • Applies to:
  • Operations Automation
  • Panels
  • Virtuozzo hypervisor


Provisioning of containers based on Debian/Ubuntu through PACI is failing after the installation of PSBM Update 9.

The container is created on the node, but its hostname is the same as the hostname of the node.


The issue is caused by an error in Parallels Server Bare Metal product code, the trailing dot in the hostname is passed to the guest OS installed in the container. RHEL-based OS-es like CentOS, Fedora are tolerate with such hostnames:

[root@psbm ~]# vzctl set 100 --hostname --save
Hostname of the Container set:
Saved parameters for Container 100
[root@psbm ~]# vzctl exec 100 hostname

Meanwhile Debian-based OS-es throw error:

[root@psbm ~]# vzctl set 201 --hostname
Hostname of the Container set:
hostname: the specified hostname is invalid
Saved parameters for Container 201

It is caused by the strict validation of a hostname which is a native Ubuntu/Debian limitation - it refuses to set a hostname ending with a ".". As the result, the hostname in the virtual environment is not altered and it is shown as the hostname of the hardware node.


The issue has been acknowledged as a product defect; the fix for the request PSBM-22996 is scheduled to be included in one of the next Parallels Server Bare Metal updates.

Search Words

invalid hostname

hostname domain tld



a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 614fd0b754f34d5efe9627f2057b8642 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF