Please find below the main documentation for DA, for both your usage and your end clients’.

1. https://evo.site-helper.com/ for end-user documentation
2. https://docs.directadmin.com/changelog/ for release info

Currently our focus is on leveraging the need to replace NS2 instances as a way to soft-cutover DNS (cP to DA).

Now we’ve almost finishing the tooling required to resolve some long-standing (SOA/NS), migration-caused (dupe v6) and now-irrelevant (cP/dav) issues and legacy across the zone files.

We’re taking the opportunity to resolve problems, sanitise zones and then process the cutovers. This lets us ensure NS2-DA takes over the role from NS2-cP, compare responses against NS1-cP, finalise NS2 wave, then do the same process again for all NS1 instances. We’re doing this by-client per-nameserver, all NS2 then all NS1.

G’day,

Due to our current provider in Adelaide winding up their Server Operations by EOM February (now: March/April), we’re moving all Adelaide SA nameservers (DNS) to Perth WA, forging a new business relationship while we do so.

As we are unable to migrate images, we’ll be using templates and building out, then migrating zones.

If you have any questions or concerns, please don’t hesitate to reach out to our support crew.

Note: NS1 services in Brisbane AU will remain as-is, online and entirely unaffected.
Further: Clients using Adelaide and Singapore, your instance being moved is NS1.

This is untimely given we only moved these in July 2025, however it’s unavoidable.

Cheers,
Merlot Digital