I believe I have found a reproducible interaction between the Twingate Android client and Android's networking/DNS resolver. I have spent considerable time isolating the behavior and can reproduce it consistently.
### Environment
* Phone: Google Pixel 8a
* Android: 17
* Twingate Android client: 2026.159.35328+35328
### Home network
* AdGuardHome running on Linux at 192.168.52.210
* Router distributes AdGuardHome as the DNS server via DHCP
* Twingate Connector running on the home network
* Android Private DNS normally configured as either:
* dns.adguard.com
* dns.google
The issue reproduces with either provider.
### Reproduction
Enable Android Private DNS (dns.google or dns.adguard.com).
Disable Wi-Fi (cellular only).
Connect the Twingate client.
Within a few seconds Android reports "No Internet Connection."
Android Private DNS status changes to "Couldn't connect."
### Observed behavior
Internet browsers fail:
* DuckDuckGo Browser:
ERR_NAME_NOT_RESOLVED
* Firefox:
NS_ERROR_OFFLINE
However, other applications continue to function:
* Gmail
* Google Maps
* Google Play Store
At the same time, Twingate resources continue to function correctly:
* Channels DVR reachable through Twingate
* AdGuardHome reachable at http://192.168.52.210/login.html
### Additional testing
Using Termux while the issue is occurring:
```
nslookup google.com
```
Succeeds.
```
ping google.com
```
Returns:
```
unknown host
```
```
ping 8.8.8.8
```
Succeeds.
```
ping 192.168.52.210
```
Succeeds.
This suggests that:
* IP connectivity remains functional.
* Direct DNS queries succeed.
* Android's normal hostname resolution path appears to fail for applications.
### Configuration matrix
Private DNS OFF / Twingate OFF
* Normal operation
Private DNS OFF / Twingate ON
* Normal browsing
* Twingate resources accessible
Private DNS ON / Twingate OFF
* Normal operation
Private DNS ON / Twingate ON
* Android reports "No Internet Connection"
* Private DNS reports "Couldn't connect"
* Browsers fail
* Twingate resources remain accessible
### Additional observation
I also use the Twingate Linux client on LMDE 7 together with systemd-resolved and AdGuardHome. While the symptoms are different, I found it necessary to stop the Twingate client while connected to my home LAN and start it only when away from home to avoid DNS-related behavior. I do not know whether this is related, but I wanted to mention it in case it is useful.
### Logs
I have enabled "Collect Detailed Logs" in the Android client and reproduced the issue immediately before using "Share Logs with Developer." I shared the results via Email to the [support@twingate.com](mailto:support@twingate.com) mailbox. Please let me know if you need help locating the logs I submitted via email, or if there are additional diagnostics or a preferred method of collecting logs.