I suspect switching users to Web Connectivity LTE would fix the issue. Fixing the issue with Web Connectivity v0.4 is possible but also dubious because we cannot be sure about what the system resolver is hiding from us. We should investigate whether using Web Connectivity LTE fixes the issue.
See for example https://explorer.ooni.org/chart/mat?probe_cc=PK&since=2023-03-05&time_grain=day&axis_x=measurement_start_day&test_name=web_connectivity&domain=www.dw.com. The issue here is that:
I suspect switching users to Web Connectivity LTE would fix the issue. Fixing the issue with Web Connectivity v0.4 is possible but also dubious because we cannot be sure about what the system resolver is hiding from us. We should investigate whether using Web Connectivity LTE fixes the issue.
Another approach would be to call connectivityManager.getLinkProperties method and then call the [linkProperties.getDnsServers method](https://developer.android.com/reference/android/net/LinkProperties#getDnsServers()) to get the DNS resolvers IP addresses.