Overview
Backup addresses let one Host keep several verified routes, such as a LAN address, public endpoint, and Tailscale address. Redock starts with the preferred route and can try an alternate when it is unavailable.
This keeps Projects, Actions, credentials, and history attached to one logical machine instead of forcing you to edit the Host address or create duplicate Host records whenever the network changes.
When to use it
- Use a fast LAN address at home or in the office, then fall back to Tailscale on cellular or outside Wi‑Fi.
- Keep both private and public routes for a server whose reachability depends on the current network.
- Move between office, home, hotel, and mobile networks without manually rewriting Host settings.
- Retain a temporary tunnel or alternate DNS name as a fallback during network maintenance or migration.
- Keep one consistent Project and Action history even when the physical route to the same machine changes.
Prefer LAN at home, fall back remotely
Use the low-latency private address on home Wi-Fi and keep Tailscale or a public endpoint as an alternate when the phone moves to cellular or another network.
Keep one logical Host during migration
While changing routers, DNS, tunnels, or server addresses, retain old and new routes together so Projects, credentials, Actions, and history remain attached to one machine.
Reduce failure during network maintenance
Add a verified secondary route before changing the primary network. If the preferred path becomes unreachable, Redock can try the alternate instead of requiring an urgent Host edit.
How it works
- Set the preferred address on the Host.
- Add one or more verified alternate addresses.
- Connect normally and let Redock try another path when the primary address is unavailable.
Practical guidance
Test every address independently before relying on fallback. An alternate route still needs valid SSH access and the same trusted Host identity.