Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS forwarding is broken since 5.0.1 #2420

Closed
4 of 18 tasks
danialbehzadi opened this issue Jan 24, 2020 · 4 comments
Closed
4 of 18 tasks

DNS forwarding is broken since 5.0.1 #2420

danialbehzadi opened this issue Jan 24, 2020 · 4 comments

Comments

@danialbehzadi
Copy link

*Describe the bug
After update to 5.0.1, DNS forwarding doesn't work. I had to downgrade to 4.8.7 in order to connect to banned websites.

Screenshots
Screenshot_۲۰۲۰۰۱۲۴-۲۱۳۳۰۵_
Screenshot_۲۰۲۰۰۱۲۴-۲۱۳۳۱۱_

Smartphone (please complete the following information):

  • Android/Chrome OS version: LineageOS 16 (AOSP 9.0.0_r46)
  • Device: Pocophone F1
  • Version: v5.0.1 and v5.0.2
  • Last version that did not exhibit the issue: 4.8.7

Configuration
Put an x inside the [ ] that applies.

  • IPv4 server address
  • IPv6 server address
  • Client IPv4 availability
  • Client IPv6 availability
  • Encrypt method: chacha20 + v2ray
  • Route
    • All
    • Bypass LAN
    • Bypass China
    • Bypass LAN & China
    • Bypass LAN & Iran
    • GFW List
    • China List
    • Custom rules
  • IPv6 route
  • Apps VPN mode
    • Bypass mode
  • Remote DNS: 8.8.8.8
  • DNS over UDP
  • Plugin configuration (if applicable):
  • Auto Connect
  • TCP Fast Open
@Mygod
Copy link
Contributor

Mygod commented Jan 24, 2020

What's bypass LAN & Iran?

Hostname matching is currently buggy from v5.0.0 to v5.0.2 which should be fixed (see also #2411). On the other hand, since 10.10.34.35 is a LAN address, it is incorrectly bypassed. If you configured the bypass Iran acl correctly, this issue should be fixed in the next version.

@danialbehzadi
Copy link
Author

10.10.0.0 is not a LAN network. It's the censorship network in Iran. If DNS resolving work correctly over shadowsocks, it should return the actual IP of twitter, but since it's not going to be resolved over shadowsocks, the Iran firewall spoofs the DNS request and returns the censored IP (10.10.34.35) instead.

@Mygod
Copy link
Contributor

Mygod commented Jan 26, 2020

Please try v5.0.3.

@Mygod Mygod closed this as completed Jan 26, 2020
@danialbehzadi
Copy link
Author

Fix in 5.0.3 confirmed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants