I’m guessing my local POP for cloudflare-dns.com had just updated their SSL cert to the one issued by SSL.com, because my DNS resolution suddenly stopped at 2026-01-15 21:42:52 UTC+0 with plenty of the following error flooding my ROS log:
DoH server connection error: SSL: ssl: no trusted CA certificate found (6)
I don’t have historical info on what the previous CA was, but for now I can see it’s using one that isn’t in the ROS 7.20.4.
If you don't want to manually add the CA cert, and want to wait for the update from MikroTik, you can change the DoH URL to https://mozilla.cloudflare-dns.com/dns-query. It's still Cloudflare, but with better privacy/less data collection. It's the URL used by Firefox when you select Cloudflare as DoH provider in the browser.
Thanks! Yesterday the issue with DoH also started on my RB5009. When this happens, the router completely loses the ability to resolve DNS, even after disabling DoH and rebooting, the problem persists. It’s quite strange.
I tried switching DoH to https://mozilla.cloudflare-dns.com/dns-query, but unfortunately it didn’t resolve the issue for me. I had DigiCert Global Root G2 installed.
Steps that actually solved it for me:
Temporarily disabled DoH verification / added fallback DNS 1.1.1.1 to restore resolution
Removed fallback DNS after DoH started working again
/ip dns set verify-doh-cert=no
/ip dns set servers=1.1.1.1
/tool fetch url="https://ssl.com/repo/certs/SSLcomRootCertificationAuthorityECC.pem"
/certificate import file-name=SSLcomRootCertificationAuthorityECC.pem
/ip dns set verify-doh-cert=yes
/ip dns set servers=""
/ip dns print
The builtin CA certificates list that was introduced just a few weeks ago was supposed to prevent this sort of problems and save the user from installing and maintaining the certificate list itself, I guess I’m back installing my own list.
You should do your own research and don’t trust me or any other random person, but I’ll share what I’m doing just in case anyone is wondering:
I saw fetched: 0 message as well. As I understand it, this is because the SSL.com ECC CA file is very small/lightweight. The file is fetched correctly (it shows up in /file print), and the import actually succeeds. After that, DoH certificate verification started working normally for me. Try /file print to list the file.
I have the same issue. I see DoH server connection error I don't know if it's related with update 7.21 because I see there are some changed related to certificates in the changelog.
With regards,
The timing is very close for both events. MikroTik released RouterOS 7.21 stable on January 12, 2026, and Cloudflare’s DoH TLS certificate chain changed shortly after, most likely around January 14, with failures noticed by January 15.
Since both happened almost at the same time, either could be a contributing factor. In any case, it definitely makes sense to check and refresh the CA certificates on the router.