Replies: 1 comment
-
Hello everyone. I think I have found the true reason for this problem. Before - I researched all my servers/logs latencies between servers and etc (my open project has 6 worldwide located servers and now project is processing several million requests in 24h). This situation gave for me some concern and every day I'm trying to research this problem. As I told earlier, problem was observed in Google Chrome for Desktop / Android configured as Customised DoH DNS.. Today I tested different DoH DNS providers in my testing environment and on my Desktop, and after half a day of work, I caught the same message - "DNS name does not resolved", in this time my browser was configured to Cloudflare DNS (1.1.1.1) and I was relieved - this is not a problem of Blocky or OS/Distros, it is a browser problem. :) Thanks for all) And thanks for Blocky, peace to all! ✌️ |
Beta Was this translation helpful? Give feedback.
-
Hello, I constantly use Blocky as DNS/DoT/DoH server for me and my friends, periodically (one of week or one in month) I receive message in my browser where I use Blocky as customised DoH server - DNS name not resolved (after refresh page, site open correctly)
I'm checking the logs and domains and servers availability - that's fine, in the Blocky logs I see success resolved statuses in time specified time range.
Maybe it is problem related to TLS handshakes or browser session terminations? Or can my server where the Block are installed be a bottleneck? What else can I look at to identify the problem?
Thank you in advance.
P.S. Browsers is Google Chrome desktop/android
Beta Was this translation helpful? Give feedback.
All reactions