No reply from NextDns.IO DNS Servers on Windows with YogaDNS

NextDNS An update on this. The ultra-low latency network option doesn't have an effect on the problem. When I ran the diag tool from an affected computer it only used anexia-dal, and the 'Pinging PoPs' section is empty. I had to change my DNS resolver to something besides NextDNS for the utility to work properly, otherwise it couldn't resolve the server names. On a computer unaffected by the problem (it's using a different network and gateway, also a unix-based OS, not Windows) the diag tool returned 10 different servers in the 'Pinging PoPs' section.

I submitted both of these reports via the diag tool. The first two letters of my email are 'jg' if this helps identify them. The first one is the problem one.

I ran the diag tool on a third computer, with the same setup as the first, problematic one (same network, YogaDNS config, Windows 10, etc.). Only this one has no problems resolving through NextDNS. I submitted its report as well, though I'm stumped as to what the difference is between the first (not working) and third (working).

Clarence I found you can temporarily work around this by adding a new server in YogaDNS > DNS servers with DNS over TLS as the protocol and changing the target server in the Rules tab. The NextDNS protocol config in YogaDNS seems to be the issue here.

NextDNS I noticed around mid afternoon (U.S. CDT) that the test computer which earlier had had the problem started working fine. I haven't tried it again this evening, but I did set up another computer with a fresh install of Windows 10 and YogaDNS 1.19 and when I first tried it it clearly exhibited the problem. All DNS requests were timing out.

One of the early lines in the log was this (config ID and machine name redacted): 

DnsCrypt log: Get https://dns.nextdns.io/XXXXX/YYYYY?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABAVSeyoQZK-BCF19wxXfaIK: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Now to answer your question, I switched DNS resolvers. The two letsencrypt.org URLs loaded fine in Chrome. (The 2nd one gave a SEC_ERROR_UNKNOWN_ISSUER warning in Firefox 89.)

The PowerShell command returned the same thing on both this new computer which had just exhibited the problem and on the other that's been working properly all day.

[Subject]
  CN=ISRG Root X1, O=Internet Security Research Group, C=US
[Issuer]
  CN=ISRG Root X1, O=Internet Security Research Group, C=US
[Serial Number]
  008210CFB0D240E3594463E0BB63828B00
[Not Before]
  6/4/2015 6:04:38 AM
[Not After]
  6/4/2035 6:04:38 AM
[Thumbprint]
  CABD2A79A1076A31F21D253635CB039D4329A5E8

After this I tried NextDNS again on the freshly installed computer and now it's working fine. So who knows...