Repository navigation
DNS resolution failure - fails to connect by hostname #3232
Description
Please read contributing guidelines. Thanks.
Describe the bug
After update to 5.3.5 app stopped working with previously valid settings. Changing hostname to IP fixes issue.
To Reproduce
Steps to reproduce the behavior:
- Add host via hostname.
- Attempt to connect (failure).
- Change hostname to IP.
- Attempt to connect (works).
Expected behavior
DNS resoloution should be working.
Smartphone (please complete the following information):
- Android/Chrome OS version: 16 (LineageOS 23.2
- Device: Sony Xperia 5 III
- Version: 5.3.5-nightly
- Last version that did not exhibit the issue: 5.3.4-nightly
Configuration
Put anxinside the [ ] that applies.
- IPv4 server address
- IPv6 server address
- Client IPv4 availability
- Client IPv6 availability
- Encrypt method: aes-256-gcm
- Route
- All
- Bypass LAN
- Bypass China
- Bypass LAN & China
- GFW List
- China List
- Custom rules
- IPv6 route
- Apps VPN mode
- Bypass mode
- Remote DNS: 127.0.0.1
- DNS over UDP
- Plugin configuration (if applicable):
- Auto Connect
- TCP Fast Open
- If you're not using VPN mode, please supply more details here:
Activity
NeuerUser commentedon Feb 20, 2026
Indeed. Just stumbled upon the same problem. The app was auto updated and all connections lost. Needed to uninstall and reinstall the last 5.3.4 version. Of course, config was lost. In the end, now everything is working again.
I guess the project seems to be pretty abandoned. Only Claude Code is releasing new versions, apparently full of bugs :-(
Mygod commentedon Feb 21, 2026
complaints are for the weak. why you no fix
CaKrome commentedon Feb 23, 2026
@Mygod The fix was already presented in #3223 (comment) on Nov 16, 2025. It's a one line change. Do you still require someone to submit a PR for this?
Mygod commentedon Feb 23, 2026
It's the wrong fix.
CaKrome commentedon Feb 23, 2026
@Mygod I have tested a version built locally with
config.put("dns", "system")and I can confirm DNS resolution of hostname works as expected. Why do you think the fix is wrong?dsamersoff commentedon Mar 3, 2026
Same here. After upgrading to 5.3.5 (on several different devices via F-Droid), it stopped working. I get the following message:
"Failed to detect internet connection: SOCKS: Network unreachable."
Replacing the hostname with the IP address fixes the issue on Huawei devices, but not on Samsung (It could be a name resolution problem on Samsung as well - didn't go too far with debugging, just downgrade).