All updates

New VPS Instances: Reliable Private DNS and an Accurate Setup Status

A new VPS keeps resolving the private hostnames of your managed databases, caches and queues, and first-boot setup now waits for, and reports, what is really happening.

Version 2.9.94Bug fixVPS

What's changed

  • New VPS instances resolve names only through the platform DNS, so the private hostnames of your databases, caches and queues no longer start failing with host not found after a while
  • Docker containers on the VPS, including those on user-defined networks, resolve those private hostnames too
  • cloud-init status --wait now waits for first-boot security hardening, so installing a package right after it no longer fails on a locked package manager
  • After a reboot the login banner no longer claims hardening is still running, and dd-hardening-status reports the real state
  • A freshly created VPS no longer reports cloud-init as degraded
  • These fixes apply to VPS instances created from 16 September onward; existing instances keep their original setup