What Problem Was the Community Trying to Solve?
The original question was not simply about getting a hostname. The user had a virtual machine at home, wanted to use it from another location, and reported that the remote method they had tried was not working. They asked whether No-IP, DuckDNS, or something similar could solve the problem.
An IceWhale team reply correctly asked for more detail: remote access depends on how the VM needs to be reached, such as SSH, remote desktop, or another application protocol. The thread did not receive those details, so it did not arrive at a confirmed configuration.
Start with ZimaOS Remote Access
Current ZimaOS documentation provides a built-in Remote Access feature. When enabled in Settings > Network and paired through ZimaClient, ZimaOS can establish remote connectivity without requiring the user to configure traditional router port forwarding for the ZimaOS dashboard.
Review the current ZimaOS Remote Access guide before adding another public-access method.
What Do No-IP and DuckDNS Actually Do?
Dynamic DNS services such as No-IP and DuckDNS keep a hostname associated with a changing public IP address. That can make a home connection easier to find, but DDNS alone does not provide authentication, encryption, a firewall rule, or a route through carrier-grade NAT.
ZimaOS currently lists DuckDNS as an App Store option. If you use DDNS, treat it as the naming layer and pair it with an appropriate secure access method such as a VPN or a properly configured TLS reverse proxy for the service you intend to expose.
Why the VM Access Method Matters
| Goal | What must be defined |
|---|---|
| SSH into a Linux VM | The VM address, SSH service, authentication, and secure network path |
| Remote desktop | The VM's remote-desktop service and a protected way to reach it |
| Open a web application | The application port plus VPN or reverse-proxy/TLS configuration |
| Reach the ZimaOS dashboard | ZimaOS Remote Access can normally be used without exposing the dashboard directly |
What Should You Check If Built-In Remote Access Is Not Working?
- Confirm Remote Access is enabled under ZimaOS network settings.
- Confirm ZimaClient can connect to the ZimaOS device locally first.
- Identify whether you need the ZimaOS dashboard itself or a service running inside the VM.
- Determine whether the internet connection uses CGNAT or another topology that prevents direct inbound connections.
- Avoid exposing SSH, RDP, or an application port to the public internet without appropriate authentication and encryption.
Frequently Asked Questions
Will DuckDNS or No-IP fix every ZimaOS remote-access problem?
No. DDNS solves hostname-to-IP mapping. It does not by itself solve blocked inbound connectivity, CGNAT, authentication, encryption, or VM routing.
Does ZimaOS have its own remote-access feature?
Yes. Current ZimaOS documentation describes built-in Remote Access through ZimaClient and the Network settings.
Can I use DuckDNS with ZimaOS?
DuckDNS is currently available in the ZimaOS App Store. It can keep a hostname pointed to a changing public address, but it should be combined with an appropriate secure access layer.
