DNS and device names
Mesh network DNS lets you reach services by device name. First confirm that devices can communicate over mesh IPs, then check name resolution, so you don’t mistake a connection problem for a DNS problem.
Set mesh network DNS in the console
Sign in to the Wanflow Console, click 万联组网 (FlowMesh) in the left navigation, open the target mesh network, and go to the DNS tab:
| Setting | Description |
|---|---|
| 组网域名 (Mesh domain) | Devices in the mesh network use this domain to address each other; the full name is “device name.mesh domain”. Click 复制 (Copy) to get it |
| DNS 服务器 (DNS servers) | Global recursive servers; DNS queries from all devices in the mesh network are forwarded here. Supports IP addresses or DoH addresses starting with https://. When 覆盖终端本地 DNS (Override device local DNS) is checked, the mesh network takes over the clients’ local DNS |
| 分域名 DNS (Split DNS) | Assigns a different resolver to specific domains, commonly used for internal domains, for example sending corp.internal to 10.0.0.53 |
| 搜索域 (Search domains) | Domain suffixes automatically appended to short hostnames. For example, after configuring corp.internal, you can use db instead of db.corp.internal |
For example, if the mesh domain is example.mesh.wanflow.com, the full name of device office-server is office-server.example.mesh.wanflow.com. Each mesh network has a different domain; use what the console shows.
Check the current configuration on Linux
On a connected Linux device, run:
flowmesh dns status
flowmesh status --jsonCheck whether DNS is enabled, and the upstream resolvers and search domains. You can get the device’s full DNS name from DNSName in the status output; don’t treat the control server’s domain as the mesh network DNS suffix.
Look up a device name
Replace the example office-server.example.mesh.wanflow.com with the actual full DNS name:
flowmesh dns query office-server.example.mesh.wanflow.com aCheck that the response code and address are as expected. This command queries the built-in resolver directly; read the result even if the command exits normally, because a failed lookup isn’t necessarily indicated by a non-zero exit code.
flowmesh ping can resolve names from the node list, so a successful probe by name doesn’t on its own prove that DNS is configured correctly for browsers or other system applications.
Linux system DNS
To accept the DNS configuration:
sudo flowmesh set --accept-dns=trueIf /etc/resolv.conf is a regular file, the client points it at the built-in resolver 100.100.100.100 and backs up the original configuration. The original configuration is restored when the service stops.
If /etc/resolv.conf is a symlink managed by systemd-resolved, resolvconf or NetworkManager, FlowMesh doesn’t overwrite it and reports this in Health in the status. In that case, configure resolution forwarding for the mesh domain through the system’s existing DNS manager; you can turn off automatic takeover first so you don’t mistakenly assume the setting has taken effect:
sudo flowmesh set --accept-dns=falseAfter turning it off, you can still query 100.100.100.100 directly for known mesh network records, but that resolver no longer forwards external domains. Don’t set it as the machine’s only public DNS.
Differences on OpenWrt
OpenWrt keeps dnsmasq managing DNS by default and turns off automatic takeover. If LAN devices need to resolve mesh network names, configure conditional forwarding for the actual mesh network suffix and verify from a LAN device. Check flowmesh dns status first; don’t guess the domain suffix.
Common problems
| Symptom | What to check |
|---|---|
| IP works, name doesn’t | Whether system DNS actually uses the mesh network resolver |
| Full name resolves, short name fails | Whether the system search domains are configured correctly |
dns query returns results, but the browser fails | System resolver configuration, the browser’s built-in DNS, and caches |
| External domains fail to resolve after switching exits | Exit online status, DNS proxy and access policy |
| External domain lookups fail after turning off accept DNS | Expected: the built-in resolver doesn’t forward external domains in this case |
Next: Troubleshoot connections.