r13 Posted February 15, 2022 Posted February 15, 2022 @Le ecureuil Сегодня в очередной раз что-то съехало в новом ДНС прокси, в логе множественные записи вида [I] Feb 15 20:38:13 ndnproxy: rogue answer from 127.0.0.1:40548 (expect from 127.0.0.1:40552), ignore. И dns стал полностью не рабочим, резолвинг не работал Поудалял doh, думал может это перезагрузит сервис, нет, не помогло. Селфтест следом Quote
0 Le ecureuil Posted February 18, 2022 Posted February 18, 2022 Но в конфиге нет ничего про DoH и никаких фильтров. Тогда откуда там записи про DoH? Quote
0 r13 Posted February 18, 2022 Author Posted February 18, 2022 (edited) Как написал выше в моменте борьбы с проблемой doh были грохнуты(как возможный источник проблемы), но нет, не помогло Изначальный конфиг был типа такого Скрытый текст dns-proxy proceed 1 rebind-protect auto tls upstream 8.8.8.8 sni dns.google.com tls upstream 8.8.4.4 sni dns.google.com tls upstream 1.1.1.1 sni cloudflare-dns.com tls upstream 1.0.0.1 sni cloudflare-dns.com tls upstream 9.9.9.9 sni dns.quad9.net tls upstream 149.112.112.112 sni dns.quad9.net https upstream https://dns.quad9.net/dns-query dnsm https upstream https://1.1.1.1/dns-query dnsm https upstream https://8.8.8.8/dns-query dnsm 24 минуты назад, Le ecureuil сказал: Но в конфиге нет ничего про DoH и никаких фильтров. Тогда откуда там записи про DoH? Edited February 18, 2022 by r13 Quote
0 vasek00 Posted February 18, 2022 Posted February 18, 2022 (edited) dns-proxy rebind-protect auto https upstream https://dns.google/dns-query dnsm on ISP https upstream https://cloudflare-dns.com/dns-query dnsm on ISP dns_server = 127.0.0.1:40508 . # https://dns.google/dns-query@dnsm dns_server = 127.0.0.1:40509 . # https://cloudflare-dns.com/dns-query@dnsm DNS Servers Ip Port R.Sent A.Rcvd NX.Rcvd Med.Resp Avg.Resp Rank 127.0.0.1 40508 5 2 3 135ms 125ms 3 127.0.0.1 40509 151 148 3 32ms 39ms 10 [W] Feb 18 00:47:18 https-dns-proxy: 2C2E: curl request failed with 0: No error [W] Feb 18 00:47:18 https-dns-proxy: 2C2E: curl error message: Failed to connect to cloudflare-dns.com port 443 after 1146 ms: Operation timed out [W] Feb 18 00:47:18 https-dns-proxy: 8218: curl request failed with 0: No error [W] Feb 18 00:47:18 https-dns-proxy: 8218: curl error message: Failed to connect to dns.google port 443 after 1219 ms: Operation timed out [W] Feb 18 00:47:18 https-dns-proxy: 4E44: curl request failed with 0: No error [W] Feb 18 00:47:18 https-dns-proxy: 4E44: curl error message: Failed to connect to dns.google port 443 after 1025 ms: Operation timed out [W] Feb 18 00:47:19 https-dns-proxy: 66A6: curl request failed with 0: No error [W] Feb 18 00:47:19 https-dns-proxy: 66A6: curl error message: Failed to connect to dns.google port 443 after 563 ms: Operation timed out [W] Feb 18 00:47:19 https-dns-proxy: 487B: curl request failed with 0: No error [W] Feb 18 00:47:19 https-dns-proxy: 487B: curl error message: Failed to connect to cloudflare-dns.com port 443 after 1252 ms: Operation timed out [W] Feb 18 00:47:19 https-dns-proxy: 3621: curl request failed with 0: No error [W] Feb 18 00:47:19 https-dns-proxy: 3621: curl error message: Failed to connect to cloudflare-dns.com port 443 after 1266 ms: Operation timed out [W] Feb 18 00:47:19 https-dns-proxy: DE0E: curl request failed with 0: No error [W] Feb 18 00:47:19 https-dns-proxy: DE0E: curl error message: Failed to connect to cloudflare-dns.com port 443 after 1142 ms: Operation timed out [W] Feb 18 00:47:19 https-dns-proxy: 2E0A: curl request failed with 0: No error [W] Feb 18 00:47:19 https-dns-proxy: 2E0A: curl error message: Failed to connect to dns.google port 443 after 1839 ms: Operation timed out [W] Feb 18 00:47:19 https-dns-proxy: 1D10: curl request failed with 0: No error ю... [W] Feb 18 00:47:26 https-dns-proxy: DC61: curl error message: Failed to connect to cloudflare-dns.com port 443 after 1325 ms: Operation timed out [W] Feb 18 00:47:26 https-dns-proxy: A822: curl request failed with 0: No error [W] Feb 18 00:47:26 https-dns-proxy: A822: curl error message: Failed to connect to dns.google port 443 after 1435 ms: Operation timed out [W] Feb 18 00:47:26 https-dns-proxy: 416F: curl request failed with 0: No error [W] Feb 18 00:47:26 https-dns-proxy: 416F: curl error message: Failed to resolve host 'dns.google' with timeout after 1000 ms [W] Feb 18 00:47:26 https-dns-proxy: AAE2: curl request failed with 0: No error [W] Feb 18 00:47:26 https-dns-proxy: AAE2: curl error message: Failed to resolve host 'dns.google' with timeout after 1000 ms [W] Feb 18 00:47:26 https-dns-proxy: BC0A: curl request failed with 0: No error [W] Feb 18 00:47:26 https-dns-proxy: BC0A: curl error message: Failed to connect to cloudflare-dns.com port 443 after 906 ms: Operation timed out [W] Feb 18 00:47:26 https-dns-proxy: 4AC5: curl request failed with 0: No error [W] Feb 18 00:47:26 https-dns-proxy: 4AC5: curl error message: Failed to connect to cloudflare-dns.com port 443 after 1371 ms: Operation timed out ... [W] Feb 18 00:53:20 https-dns-proxy: E1E2: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received [W] Feb 18 06:12:21 https-dns-proxy: 0963: curl request failed with 0: No error [W] Feb 18 06:12:21 https-dns-proxy: 0963: curl error message: Failed to connect to dns.google port 443 after 2252 ms: Operation timed out [W] Feb 18 06:12:21 https-dns-proxy: CB60: curl request failed with 0: No error [W] Feb 18 06:12:21 https-dns-proxy: CB60: curl error message: Operation timed out after 3002 milliseconds with 0 bytes received [W] Feb 18 06:12:31 https-dns-proxy: 4453: curl request failed with 0: No error ПО 38А5 на Viva Edited February 18, 2022 by vasek00 Quote
0 r13 Posted May 26, 2022 Author Posted May 26, 2022 @Le ecureuil на beta2 ошибка по прежнему присутствует. Свежий селфтест следом Quote
0 Le ecureuil Posted May 26, 2022 Posted May 26, 2022 Сообщение про "rogue answer" я подправил, но не верю что это может быть причиной что "не работает". Это, вероятно, что-то еще: и вот это непонятно. Больше похоже что интернет "застрял" и не работает. Quote
0 r13 Posted May 26, 2022 Author Posted May 26, 2022 1 час назад, Le ecureuil сказал: Сообщение про "rogue answer" я подправил, но не верю что это может быть причиной что "не работает". Это, вероятно, что-то еще: и вот это непонятно. Больше похоже что интернет "застрял" и не работает. Не, все работает, просто в логах много подобных записей. Quote
Question
r13
@Le ecureuil Сегодня в очередной раз что-то съехало в новом ДНС прокси,
в логе множественные записи вида
[I] Feb 15 20:38:13 ndnproxy: rogue answer from 127.0.0.1:40548 (expect from 127.0.0.1:40552), ignore.
И dns стал полностью не рабочим, резолвинг не работал
Поудалял doh, думал может это перезагрузит сервис, нет, не помогло.
Селфтест следом
6 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.