- 2
4.2 Alpha 4 Проблема с QUIC и DNS
-
Recently Browsing 0 members
- No registered users viewing this page.
This site uses cookies. By clicking "I accept" or continuing to browse the site, you authorize their use in accordance with the Privacy Policy.
Question
Robespierre
Всем привет! Наверняка вы уже слышали/читали о том, что QUIC в России работает мягко говоря не очень, и эта фича в совокупности с DoH приводит к спаму в логах, например:
[W] Apr 13 12:59:27 https-dns-proxy: 441B: 0000: 49 6e 76 61 6c 69 64 20 71 75 65 72 79 2e Invalid query. [W] Apr 13 12:59:28 https-dns-proxy: 6EEA: curl response code: 400, content length: 14 [W] Apr 13 12:59:28 https-dns-proxy: 6EEA: 0000: 49 6e 76 61 6c 69 64 20 71 75 65 72 79 2e Invalid query. [W] Apr 13 12:59:28 https-dns-proxy: CFB4: curl response code: 400, content length: 14 W] Apr 14 03:16:58 https-dns-proxy: E1FC: "https://1.0.0.1/dns-query": curl error message: QUIC connection has been shut down [W] Apr 14 03:16:59 https-dns-proxy: 8FB4: "https://1.0.0.1/dns-query": curl error message: QUIC connection has been shut down https-dns-proxy: "https://1.0.0.1/dns-query": too many failed requests, try to reload process [W] Apr 14 03:07:27 https-dns-proxy: 006D: "https://1.0.0.1/dns-query": curl error message: Operation timed out after 3000 milliseconds with 0 bytes received
Может быть, возможно как-нибудь отключить QUIC в DoH (как вариант: вынести это в отдельную функцию, типа DoQ (DNSoverQUIC), или что-нибудь подобное.
Edited by RobespierreЗамечу, что обычный DoH на обновлении 4.2 Alpha 3 работал отменно.
Ошибка в название протокола
27 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.