Innernet appears to use /etc/hosts on the clients and updates it from the server when peers are added/removed etc. To configure split DNS on the server, you'd

Innernet appears to use /etc/hosts on the clients and updates it from the server when peers are added/removed etc. To configure split DNS on the server, you'd need an authoritative server listening on the wg interface and update the zone file when peers are added and removed. To configure the split DNS on the clients: Linux: systemd-resolverd supports split DNS see https://fedoramagazine.org/systemd-resolved-introduction-to-split-dns/ https://fedoramagazine.org/systemd-resolved-introduction-to-... MacOS: Supports similar split DNS by domain/interface, see resolver(5) for the details. Windows: I'm not a windows person, but it appears that Windows has trouble and you need to play with interface metrics, one solution was to install unbound and use it instead of Windows' native resolver.