Potential DNS issue using PIA on 4.0

[DrR0Ck]

I've been running 4.0 on a Synology NAS for a month or so without issue until a couple of days ago, when the container refused to start up properly. The startup log seems to point to a DNS issue, but I am uncertain as to why this would have started suddenly, and what to do to try to resolve. Log entries below:

11/6/2021 18:22 stdout curl: (6) Could not resolve host: www.privateinternetaccess.com
11/6/2021 18:21 stdout Downloading OpenVPN config bundle openvpn into temporary file /tmp/tmp.HbT9OIbeIR
11/6/2021 18:21 stdout Executing setup script for PIA
11/6/2021 18:21 stdout Provider PIA has a bundled setup script. Defaulting to internal config
11/6/2021 18:21 stdout Running with VPN_CONFIG_SOURCE auto
11/6/2021 18:21 stdout Using OpenVPN provider: PIA
11/6/2021 18:21 stdout mknod: /dev/net/tun: File exists
11/6/2021 18:21 stdout Creating TUN device /dev/net/tun
11/6/2021 18:21 stdout WARNING: initial DNS resolution test failed
11/6/2021 18:21 stdout Starting container with revision: e6fd367

The one thing I did try was to set the PEER_DNS value to false from current setting of true, but this did not have any impact. I'm not ware of any issues on the PIA side of things. Any troubleshooting help would be appreciated. Let me know if there is additional info I can provide to assist with troubleshooting.

Thanks!

[DrR0Ck]

Well, I seem to have gotten things working. I was using the PIA DNS servers for DNS, specified in my resolv.conf file. I changed these to the Google DNS servers and I'm back in business. PIA recently rolled out a SmartDNS service, so I suspect the new service has something to do with their DNS servers no longer working as desired. I'll probably dig a bit deeper as to what's going on with their DNS servers, but given I am up and running, it's become less urgent.