DNS (without setting it) fails lookup, resulting in ping healthcheck failing

[zilexa]

bash-5.1# ping -c 1 www.google.com
ping: bad address 'www.google.com'
bash-5.1# nslookup www.google.com
;; connection timed out; no servers could be reached

bash-5.1# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=116 time=11.688 ms
64 bytes from 8.8.8.8: seq=1 ttl=116 time=11.884 ms

Pinging an IP address works fine, but pinging a domain does not. NSlookup is not possible.
Strange right?

I did not set the VPNDNS variable in Compose. I expect this not to be necessary, its optional and PIA has its own DNS.

When I do set VPNDNS to my own dns server or a public one, nslookup works.

Did something change at PIA side and does this container require updating to make PIA own DNS work again?

[thrnz]

If VPNDNS is not specified then the container defaults to using PIA's. The container log should show:
Using PIA DNS servers: 10.0.0.243,10.0.0.242
Otherwise check /etc/resolv.conf to confirm whats being used once the vpn is up.

One thing that comes to mind is if that overlaps with a LOCAL_NETWORK range then it might end up inaccessible.

[zilexa]

I'll test but that must be the cause because 10.0.0.0/24 is my own wireguard VPN network range, indeed what I added in compose as well. This must be the culprit!
I guess I either change my VPN address range or instead use my own DNS server (Adguard Home with Klutchell Unbound image, as my upstream DNS server).