Brad House

any update on this PR with my latest feedback ?

on point 2, if it works on msvc *and* everything else to put the attribute up front, then it seems like what we'll need. Otherwise we'll have to figure out...

moved to PR #732

Yeah, if #611 is implemented (the eventloop thread), it would have a thread constantly running for any `ares_channel_t` (optionally, of course ... but it would be a requirement to use...

Its not _**that**_ complex :) HPACK is probably the most non-obvious component. But for as small a subset of HTTP/2 we'd need for DoH it doesn't make sense to bring...

I'll admit I have a bit of a "not-invented-here" syndrome when it comes to 3rd party C code :) But in my defense, I think C has earned the reputation...

RFC 8484 says the minimum version is HTTP/2. I'd be ok with that limitation and not support some odd provider that only supports HTTP/1.1. HTTP/2 is required for async requests...

I'd probably replace the solution I use in mstdlib (https://github.com/Monetra/mstdlib) with the native c-ares one if it existed. It might also help spur more adoption of happy eyeballs in other...

This appears to use the registry key of `HKLM\Software\Policies\Microsoft\Windows NT\DNSClient\AppendToMultiLabelName`, which is part of the group policies, and will override local machine configuration. We aren't actually reading the local machine...

A big example of something on Windows we don't support is this https://learn.microsoft.com/en-us/powershell/module/dnsclient/add-dnsclientnrptrule?view=windowsserver2022-ps#examples (Example #2), where you can specify a domain-specific DNS server. MacOS also supports a similar concept: https://apple.stackexchange.com/questions/366914/using-scutil-to-set-dns-for-specific-domains