Mikrotik: DoH server connection error: Idle timeout - connecting

Hi, @nextdns
I'm frequently seeing "DoH server connection error: Idle timeout - connecting" errors on my RB5009 Mikrotik's 7.1x log.
I tried setting, both TCP and DoH, max server connections to 10 or 20, and max concurrent queries to 500 or 1000, but still got the same errors. DoH timeout is 5 s (5.000 ms).
Apparently I can't reach out dns2.nextdns.io (45.90.30.0)
I have no timeouts if I switch to Cloudflare DoH or Google DoH.
https://nextdns.io/diag/919b9bd0-dccf-11ef-91bb-efb077657c82
Thanks in advance,
Rodrigo
4 replies
-
Hi @NextDNS / @nextdns_network ,
I've contacted my ISP and they fixed the IPv4 routing to anycast.dns2.nextdns.io but now the anycast is redirecting to higher latency servers then it should (AMS instead of SAO or RIO and BSB).
Can you please adjust it?
https://nextdns.io/diag/eaa76a10-df2c-11ef-b1b6-8d88e2ece88a
https://ping.nextdns.io/Thanks,
Rodrigo -
Using DoH I'm able to force it to use anycast1 with single digit latency.
I had to restrict it only to anycast1 because anycast2 is across the ocean,
with a 20x higher latency.
But I can't enforce my profile on a fixed server over TLS or QUIC (natively on android).
Automatically, ultralow isn't picking the closest server.
Please, take a look on both issues (anycast2 and ultralow).
Thanks,
Rodrigo
-
Hi Rodrigo
If you write in the static DNS address 45.90.30.0 and 45.90.28.0 as well as IPv6, you force the router Mikrotik itself to go to this IP to receive responses from DNS servers even if it is not optimal in speed or proximity, look for the IP address that you get the best in the tests and enter it in the router settings.
Content aside
- 3 wk agoMon, February 17, 2025 at 12:17 PM UTCLast active
- 4Replies
- 281Views
-
2
Following