Please read contributing guidelines. Thanks.
Describe the bug
unable to resolve hostname with smartDNS on remote server on 5.13.
but 5.12 is fine.
smartDNS listen to udp DNS request on 53.
also
smartDNS listen to tcp DNS request on 53.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
5.12 and below works fine with the mentioned process.
And 5.13 can not resolve DNS no matter set remote DNS to 0.0.0.0/127.0.0.1 or 8.8.8.8/1.1.1.1 .
pls, fix it.
Smartphone (please complete the following information):
Configuration
Put an x inside the [ ] that applies.
relate issue
I think you remove the DNS forward through udp.
However, the DNS forward through tcp also failed.
Cannot reproduce locally.
In fact, nothing changed in DNS module from 5.1.2 to 5.1.3.
Logcat?
Hi, @Mygod , @madeye
how can I export the local logcat from ss?
5.13 with the same profile and clean install

5.12 with KCPTUN plugin

what goes wrong?
The kcptun plugin looks out of date, nothing wrong with the DNS logic.
Try this kcptun apk
We can use the plugin version code to identify legacy behavior. @madeye
Thanks, everyone.
This is the kcptun plugin bug.
Blew fix it.
Try this kcptun apk
Same issue here.
Fixed with new kcptun plugin apk.
Try this kcptun apk
V2ray plugin have same problem with 5.13
I think https://github.com/shadowsocks/shadowsocks-android/issues/2582 is the same problem
Will you update the simple-obfs-android apk since simple-obfs plugin have the same issue with the new version 5.1.3.
We can use the plugin version code to identify legacy behavior. @madeye
@madeye How about only using the new behavior for plugin 1.4.+?
Also we should do a new release with this fix: https://github.com/shadowsocks/shadowsocks-rust/commit/5af929004e3bef4d330de277de8a3fb32ce961b3
@Mygod Not sure how to do that. Can you submit a pull request?
Yeah, we can schedule a release this week.
You can try to look at the app's metadata?
It seems not possible to me, since we need to modify shadowsocks-rust to pass -V in command line if the plugin version is lower than v1.4.
@Mygod do we have an API in PluginManager to retrieve the plugin version number?
Yes.
Okay, please help me on this. I'm not familiar with this part of code.
I guess we can fallback to pass -V to the plugin if the plugin version < 1.4
@madeye The latest version of Kcptun on Google Play store is 1.0.0, would you mind publishing the above newer version onto Play store?
Same issues here with v2ray-plugin 1.3.2. I checked v2ray-plugin-android but no update yet. Will there any update with it soon?
@skyred Join the beta channel or download the apk directly from here: https://github.com/shadowsocks/kcptun-android/releases/tag/v1.0.1
@skyred Join the beta channel or download the apk directly from here: https://github.com/shadowsocks/kcptun-android/releases/tag/v1.0.1
Thanks. I didn't realize there was a beta program for KCPTUN, just joined, and it works!
Most helpful comment
Will you update the simple-obfs-android apk since simple-obfs plugin have the same issue with the new version 5.1.3.