Windows Client - 1.1.1.1 Upstream DNS

[nBLnzbbBBvSGEd]

Hey,

I can't get Pangolin to connect while on a particular network. This network has blocked external DNS (1.1.1.1 included).
No matter what I change in the configs for the Windows client, the logs show:

DNS lookup failed using all upstream servers: lookup pangolin.example.com on 192.x.y.z:53: read udp 192.x.y.a:52889->1.1.1.1:53: i/o timeout

It seems to be hardcoded to use 1.1.1.1. Is it possible to change this?

[oschwartz10612]

Yeah this is a problem. It is not right now but I am adding the ability to do so shortly. Will try to remember to ping here. Sorry for the hassle

[nBLnzbbBBvSGEd]

Thanks for the clarity on that one. I wasn't sure if it was a bug, or something I was (or wasn't) doing.

No need to apologize - you have a great product.

[TjenHey]

Just came across this issue myself, I feel like the intended behavior should be that the client uses the system's DNS server by default? I think this should probably also be the default for the primary upstream DNS server, instead of also defaulting to 1.1.1.1?

[LeonvanHeerden]

I have never used the client because of this issue. I have a split DNS setup for internal and external Ips for hosts that require this. Now with the new 1.19 Private features i am having this issue again. The 1.1.1.1 is hard coded and forces the external IP to ALWAYS be found for all hosts. I have setup Hairpin NAT, but ideally i would like to use the internal IPs and block 1.1.1.1 again. My internal DNS uses it as a upstream DNS via a secure connection. This exposes traffic again.

[oschwartz10612]

In the latest releases of all of the clients (except for iOS) the client should now pull the DNS of the host to use as the upstream DNS default and the public DNS default. You can still override in the settings but if you want it to pull the host's information you can delete the primary and secondary settings. LMK if this improves.