Looking for some further guidance here on getting DNS name resolution working internally and from ext client. This is what I’ve done: - Spin up a cluster in DOKS using k8s 1.22 with two nodes - architecture looks like this: - Install netclient on both nodes using daemonset here, but update it to use v0.12.1 instead of v0.9.3 https://raw.githubusercontent.com/gravitl/netmak8s/main/netclient-daemonset.yaml. Also installed egress gateway on one node in the cluster and labelled it appropriately - Created droplet outside of DOKS VPC and installed netmaker-server on it using docker-compose, following the guide as expected except commenting out COREDNS_ADDR on docker-compose since DNS should run over wireguard. - Create a network called “internal” via server UI, and add tokens to netclient and restart deployment/daemonsets. Used range 10.11.12.0/24 - Tagged my node as egress gateway in netmaker ui, and made netmaker-server droplet the ingress gateway. Created an extended client config and installed it on my home desktop. - Verified nodes joined the network as 10.11.12.1 and 10.11.12.2. Verified that the netmaker-server is running with CoreDNS enabled on 10.11.12.254 Can ping both the nodes and the server over the internal IP’s just fine from my ext client (home-desktop). Now I attempt to resolve internal hostname from ext client: Without specifying DNS in the ext-client config on home-desktop

nslookup netmaker-1.internal 10.11.12.254 
;; connection timed out; no servers could be reached

- After specifying DNS of 10.11.12.254 in the ext-client config on home-desktop

nslookup netmaker-1.internal 10.11.12.254
;; connection timed out; no servers could be reached