as in, if I set "Default Ext Client DNS to a public dns server (like 1.1.1.1 or 8.8.8.8) it seems to work, but if I try to set an DNS server that is part of the "Egress Gateway Ranges" not so much

will try another client rather the the wireguard app on Android

Android --> Node_1 --> Node_2 --> Egress Network --> DNS Server

if that make any sense 😛

that does not make much sense to me lol

haha 😄

so is this an entirely different DNS server? like you have your own dns server you're just trying to use?

indeed

ahhh ok, I assumed we were talking about netmaker's dns server this whole time

aah, sorry, my bad, I'm terrible at explaining 😛

hmm, restarted everything, and now it works.... lol 😛 prob some stuff I missed, thanks for the help regardless 😄

weird...lol. well glad it's working now

that's definitely an interesting setup, to have dns behind a gateway like that

it's pihole (https://pi-hole.net/) to block ads etc, and also as it works as an internal dns for my internal services that I wanna reach with the phone 😉

cool! any chance you'd wanna do a write up about that? I've been meaning to do something with pi hole but havent had the time

Well regarding pihole, if you configure coredns config as volume, available on the host / pihole docker, you can reference the netmaker dns file in dnsmasq from pihole. So pihole is resolving your internal lan and the vpn nodes. Reverse lookup should work also. But external clients are not configured/listed in coredns file in actual version, as @jolly-london-20127 told me . You can also reference the netmaker dns Server/Port in dnsmasq/pihole via Server=//: And for reverse: Rev-server = //: Hope I remembered the parameters correctly

hmm, interesting... that would be a very nice setup.. sort of "two ways"

I'm running pihole in containers, so sharing the files shouldn't be too much of change

Yes it is working at my place.

sweet

Another way could be to query the api of netmaker and build a dns hosts file on a host != netmaker host

or just point to tcoredns for the whole tld

not as dynamic but don't need to do any extra setup

Dnsmasq is often compiled with inotify so it reload automatically if a file in a specified directory changes

I think I did not get your idea

I have disabled my coredns docker and use the config file for coredns in dnsmasq

make the pihole just ask the coredns dns server for request for the *.networkname

when PC_b, PC_c are in the same LAN(behind NAT). when 'udp hole punching' is open, nc will use the local ip, but the puclic port for LAN.

PC_a interface: nm-home listening port: 51822 peer: XXXX endpoint: 113.87.13.72:30466 allowed ips: 10.0.0.3/32 latest handshake: 1 minute, 2 seconds ago peer: XXX endpoint: 113.87.13.72:32252 allowed ips: 10.0.0.2/32 latest handshake: 1 minute, 14 seconds ago PC_b interface: nm-home listening port: 56171 peer: XXX endpoint: 192.168.3.82:30466 no handshake peer: XXX endpoint: XX.XXX.XX.XX:51822 latest handshake: 1 minute, 16 seconds ago PC_c interface: nm-home listening port: 62343 peer: XXX endpoint: 192.168.3.80:32252 no handshake peer: XXX endpoint: XX.XXX.XX.XX:51822 latest handshake: 1 minute, 16 seconds ago

Yes my internal pihole dnsmasq does exactly that. I configured the pihole ip as my DNS Server for netmaker nodes and external clients