Routes and DNS
Two things people expect from a private network: reach the office subnet without installing anything on every printer, and call machines by name.
Network routes
A routing peer sits inside a network and forwards traffic for it. Publish the subnet in Network Routing → Routes → Add route:
| Field | Value |
|---|---|
| Network | the subnet behind the peer, for example 192.168.10.0/24 |
| Routing peer | a Linux peer inside that subnet with IP forwarding allowed |
| Distribution groups | which devices receive the route |
| Masquerade | on, unless the subnet's routers know how to send replies back to the mesh |
| Metric | lower wins when two peers publish the same subnet (that is also how you get failover) |
Devices in the distribution groups can then reach 192.168.10.x as if they were on site. Access-control policies still apply to the routing peer.
The default route 0.0.0.0/0 is a special case: an exit node.
Names for peers
Every peer gets a name under your network's domain, laptop.tzxmesh.internal by default; set your own suffix in Settings → DNS domain. Names resolve on every device without touching its resolver configuration by hand.
Nameservers
DNS → Nameservers pushes resolvers to groups of devices: all queries, or only the domains you list (split DNS). Typical use: the office domain resolves through the office DNS server, reachable over a route; everything else stays with the device's normal resolver.
DNS routes
Instead of a subnet, a route can name domains: traffic to *.internal.example.com goes through the routing peer, whatever addresses those names resolve to. Handy when a provider keeps changing IPs.