Closed Atlantis829 closed 5 months ago
i'm also facing the same.
I have the same confusion.
What's ur upstream dns? Try add https://223.5.5.5/dns-query into ur list ,if u in China.
What's ur upstream dns? Try add https://223.5.5.5/dns-query into ur list ,if u in China.
Yes, but I think the DNS providers in Chinese Mainland have pollution problems, so I will not use the service providers in Chinese Mainland. This is Alibaba's server, and there should be polluted information
What's ur upstream dns? Try add https://223.5.5.5/dns-query into ur list ,if u in China.
Yes, but I think the DNS providers in Chinese Mainland have pollution problems, so I will not use the service providers in Chinese Mainland. This is Alibaba's server, and there should be polluted information
That's the point, but other services like 1111 or 8888 have connection problem here. Try to use the dnsmasq-china-list to accelerate. For example:
[/biblibili.com/biliapi.com/biliapi.net/biliaudiocdn.xyz/bilibii.com/bilibil.com/bilibili.cc/bilibili.co/bilibili.com/bilibiligame.net/bilibilihelper.com/bilibilijj.com/bilibilis0.one/bilibiliyoo.com/bilicdn1.com/bilicdn2.com/bilicomic.com/bilicomics.com/biligame.com/biligame.net/bilihot.com/biliimg.com/bilimoe.com/bilive.com/bilivideo.com/]https://223.5.5.5/dns-query
use alidns to resolve bilibili.
Acceptable speed.
Acceptable speed.
When I use tls8.8.4.4(Google),it's just 30ms so quickly,but if in the fastest model,it will be 40s+
That's weird. I use tls 1.1.1.1 and 1.0.0.1 with parallel mode, and works fine, 8.8.8.8 not work here, cant pass upstream test.
If you use the "Fastest ip"mode, it will queue for all the server and wait for them response. dns.google is not stable in China, so you will get the 40s wait.Try to use parallel mode maybe.
If you use the "Fastest ip"mode, it will queue for all the server and wait for them response. dns.google is not stable in China, so you will get the 40s wait.Try to use parallel mode maybe.
This is not surprising. This is caused by the differences in the network environment in various parts of China. For example, in China Mobile Network, 1.1.1.1 is not accessible, while 1.0.0.1 is available (19ms). You can use port scanning. I tested Google dns in most network environments, and the results are as follows: 8.8.8.8's 443 (https) and 853 (tls) ports are not available, 53 ports are available, 8.8.4.4's 853 and 53 ports are available, 443 is not available (that's why I choose tls://8.8..4.4 , even if the network environment is changed, it can still be used). In addition, I recommend a service tls of 中華電信that I have been using tls://101.101.101.101,As for 40s, I think it is a software design problem. It should be abandoned when some IP addresses are unavailable
Should set a value of timeout, avoid this kind of situation.
yep i already set but donnot work
Hi, are you still experiencing this?
Prerequisites
[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to request a feature or enhancement and not ask a question
Description
What problem are you trying to solve?
Hello, sorry to bother you, I searched the wiki for this problem but couldn't find any solution. When it is selected as the fastest IP mode, the dns resolution time will reach 40 seconds when the expiration time is set to 1 second, which is unreasonable. At the same time, when it is set to 400ms or even lower, there is no query record in dns, so we cannot Ensure that each dns server can be connected smoothly, but I can at least ensure that among the dozens of servers in my upstream dns list, there will always be a few servers that can maintain connections, but this connection is not fixed. I want to give up waiting after it waits 1 second and pick the fastest IP address instead of 40 seconds. (When selecting simultaneous query, the parsing time is 100 milliseconds or even lower), can you help me solve this proble m? [thanks]