Private resource DNS aliases don't resolve on the Android app. I created a private resource and turned on DNS alias override on the Android and Windows apps. The Android one fails to resolve any alias I give it, while the Windows one has no problems doing so. I haven't turned on private DNS or anything like that on the phone, all such settings are basically factory default.
Environment
OS Type & Version: (e.g., Ubuntu 22.04) Android 15 with app version 0.1.10
Pangolin Version: 1.17.0
Gerbil Version: 1.3.1
Traefik Version: 3.6
Newt Version: 1.11.0
Olm Version: (if applicable)
Basically latest of everything.
To Reproduce
Create private resource, connect on the Android app, and hit the alias you gave the private resource. You should see an error akin to EIA, i.e it can't resolve the alias.
I tried this with .local and .test domains that otherwise don't exist on the network, so they can only come from Pangolin.
Expected Behavior
It should hit the private resource.
Originally created by @Zeilar on GitHub (Apr 12, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2840
### Describe the Bug
Private resource DNS aliases don't resolve on the Android app. I created a private resource and turned on DNS alias override on the Android and Windows apps. The Android one fails to resolve any alias I give it, while the Windows one has no problems doing so. I haven't turned on private DNS or anything like that on the phone, all such settings are basically factory default.
### Environment
- OS Type & Version: (e.g., Ubuntu 22.04) Android 15 with app version 0.1.10
- Pangolin Version: 1.17.0
- Gerbil Version: 1.3.1
- Traefik Version: 3.6
- Newt Version: 1.11.0
- Olm Version: (if applicable)
Basically latest of everything.
### To Reproduce
Create private resource, connect on the Android app, and hit the alias you gave the private resource. You should see an error akin to EIA, i.e it can't resolve the alias.
I tried this with .local and .test domains that otherwise don't exist on the network, so they can only come from Pangolin.
### Expected Behavior
It should hit the private resource.
In typical fashion it started working a while later when I tried again, not sure what changed, but it seems to work as expected now.
Having said that, the Android app does feels somewhat unstable. I enabled logs and it says it's still disabled, and at one point the app was stuck in a spinner page forever (even after restart) and if you set another VPN on your device as "always on", Pangolin would silently fail when you connect.
<!-- gh-comment-id:4232405731 -->
@Zeilar commented on GitHub (Apr 12, 2026):
In typical fashion it started working a while later when I tried again, not sure what changed, but it seems to work as expected now.
Having said that, the Android app does feels somewhat unstable. I enabled logs and it says it's still disabled, and at one point the app was stuck in a spinner page forever (even after restart) and if you set another VPN on your device as "always on", Pangolin would silently fail when you connect.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Zeilar on GitHub (Apr 12, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2840
Describe the Bug
Private resource DNS aliases don't resolve on the Android app. I created a private resource and turned on DNS alias override on the Android and Windows apps. The Android one fails to resolve any alias I give it, while the Windows one has no problems doing so. I haven't turned on private DNS or anything like that on the phone, all such settings are basically factory default.
Environment
Basically latest of everything.
To Reproduce
Create private resource, connect on the Android app, and hit the alias you gave the private resource. You should see an error akin to EIA, i.e it can't resolve the alias.
I tried this with .local and .test domains that otherwise don't exist on the network, so they can only come from Pangolin.
Expected Behavior
It should hit the private resource.
@Zeilar commented on GitHub (Apr 12, 2026):
In typical fashion it started working a while later when I tried again, not sure what changed, but it seems to work as expected now.
Having said that, the Android app does feels somewhat unstable. I enabled logs and it says it's still disabled, and at one point the app was stuck in a spinner page forever (even after restart) and if you set another VPN on your device as "always on", Pangolin would silently fail when you connect.