DNS over HTTPS
>  for privacy, performance and security.<p>I understand the privacy and security aspects.  But I am wondering - how can DNS over HTTPS be more performant in the case of curl commands?  A browser could probably persist the connection to the resolver and issue several requests together, but with a single curl command surely there's the overhead of initiating the first DNS resolve, the HTTPS connection, the second DNS resolve.  There must be some delay compared to regular DNS.<p>Side note - I just learned that performant is not a recognized word (<a href="https://english.stackexchange.com/questions/38945/what-is-wrong-with-the-word-performant" rel="nofollow">https://english.stackexchange.com/questions/38945/what-is-wr...</a>)