Dns over http2 or https? about dnscrypt-proxy HOT 11 CLOSED

I'm not even sure that Google supports this yet. They have a service that returns responses as JSON results, but the actual DoH specification requires a way more efficient, binary format.

There must be some, but I'm not aware of any public DoH servers yet, even though some implementations exist. People are probably waiting for the final specification to be published.

from dnscrypt-proxy.

Will u have plan to implement dns over tls?

from dnscrypt-proxy.

No. DNS-over-TLS is useless, and will be quickly obsoleted by DoH.

from dnscrypt-proxy.

Another question is why EDNS or SDNS? What are they? I tried Google.. I see extended dns and secure dns. Is that what they mean?

How are they got to do with DNSSEC? What is the advantage over the previous v1 with public key?

from dnscrypt-proxy.

I have no idea what SDNS is.

EDNS is a standard mechanism to add features that DNS designers didn't think about 25 years ago.

v1 was too complicated and worked with a single protocol.

from dnscrypt-proxy.

Coz I see your stamp is using sdns.
sdns://AQMAAAAAAAAAEjIxMi40Ny4yMjguMTM2OjQ0MyDoAbhOpga_sLrAzkNEW7FeumSwL6PEqjGuEGNqB5AyTR8yLmRuc2NyeXB0LWNlcnQuZnIuZG5zY3J5cHQub3Jn

So I am wondering what is this and what is the advantage in term of security and performance?

from dnscrypt-proxy.

It’s like QR code for DNS.

from dnscrypt-proxy.

In term of security and privacy, With http2, does isp know site I vistiting via dns?
Is the link between me and Google encrypted? Like dnscrypt?

What is different between dns over https and dns over http2?

from dnscrypt-proxy.

It's called DNS-over-HTTPS, but, quoting section 7.1:

   The minimum version of HTTP used by DOH SHOULD be HTTP/2 [RFC7540].

   The messages in classic UDP based DNS [RFC1035] are inherently
   unordered and have low overhead.  A competitive HTTP transport needs
   to support reordering, parallelism, priority, and header compression
   to acheive similar performance.  Those features were introduced to
   HTTP in HTTP/2 [RFC7540].  Earlier versions of HTTP are capable of
   conveying the semantic requirements of DOH but would result in very
   poor performance for many uses cases.

HTTPS and HTTP2 are commonly intercepted by middleboxes "for security". DNSCrypt is not vulnerable to this, due to the static keys. But static keys can be implemented for HTTP2 as well, and dnscrypt-proxy implements this.

from dnscrypt-proxy.

Does that mean now beta 11 is doing dns request via 443 instead of 53? In the example of using google dns (doh)

from dnscrypt-proxy.

Yes. Same as DNSCrypt.

from dnscrypt-proxy.