DNS bugs on 5.13 pls fix it.

[shell12345]

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:

1. 5.1.3
2. remote server uses smartDNS or dnsmsq to unlock stream, like Netflix
3. set remote DNS 127.0.0.1 or 0.0.0.0
4. VPN mode
5. unable to resolve hostname

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):

• Android 10
• Device: Google Pixel 3 XL
• Last version

Configuration
Put an x inside the [ ] that applies.

• [ x] IPv4 server address
• IPv6 server address
• [x ] Client IPv4 availability
• Client IPv6 availability
• Encrypt method:
• Route
  • All
  • Bypass LAN
  • Bypass China
  • [x ] Bypass LAN & China
  • GFW List
  • China List
  • Custom rules
• IPv6 route
• Apps VPN mode
  • Bypass mode
• Remote DNS: 127.0.0.1 or 0.0.0.0
• [ x] DNS over UDP
• Plugin configuration (if applicable):
• Auto Connect
• TCP Fast Open

[shell12345]

relate issue
#2564
I think you remove the DNS forward through udp.
However, the DNS forward through tcp also failed.

[madeye]

Cannot reproduce locally.

In fact, nothing changed in DNS module from 5.1.2 to 5.1.3.

[Mygod]

Logcat?

[shell12345]

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

[shell12345]

what goes wrong?

[madeye]

The kcptun plugin looks out of date, nothing wrong with the DNS logic.

[madeye]

Try this kcptun apk

kcptun-arm64-v8a-1.0.1.apk.zip

[Mygod]

We can use the plugin version code to identify legacy behavior. @madeye

[shell12345]

Thanks, everyone.
This is the kcptun plugin bug.

Blew fix it.

Try this kcptun apk

kcptun-arm64-v8a-1.0.1.apk.zip

[kn007]

Same issue here.
Fixed with new kcptun plugin apk.

Try this kcptun apk

kcptun-arm64-v8a-1.0.1.apk.zip

[kn007]

V2ray plugin have same problem with 5.13

I think #2582 is the same problem

[Mygod]

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: shadowsocks/shadowsocks-rust@5af9290

[madeye]

@Mygod Not sure how to do that. Can you submit a pull request?

Yeah, we can schedule a release this week.

[Mygod]

You can try to look at the app's metadata?

shadowsocks-android/plugin/src/main/AndroidManifest.xml

Line 5 in 1783420

<meta-data android:name="com.github.shadowsocks.plugin.version"

[madeye]

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.

[madeye]

@Mygod do we have an API in PluginManager to retrieve the plugin version number?

[Mygod]

Yes.

[madeye]

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

[skyred]

@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?

[Darnix]

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?

[madeye]

@skyred Join the beta channel or download the apk directly from here: https://github.com/shadowsocks/kcptun-android/releases/tag/v1.0.1

[skyred]

@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!