search

DNSCrypt / dnscrypt-resolvers

Lists of public DNSCrypt / DoH DNS servers and DNS relays
https://dnscrypt.info
1.22k stars 261 forks source link

odoh-crypto-sx does not have an ODoH configuration #510

Closed syphyr closed 3 years ago

syphyr commented 3 years ago

When testing odoh-crypto-sx, I get the following startup error:

Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] dnscrypt-proxy 2.0.46-beta1 Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Network connectivity detected Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Using systemd sockets Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Wiring systemd TCP socket #0, dnscrypt-proxy.socket, 127.0.0.1:5454 Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Wiring systemd UDP socket #1, dnscrypt-proxy.socket, 127.0.0.1:5454 Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Wiring systemd TCP socket #2, dnscrypt-proxy.socket, [::1]:5454 Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Wiring systemd UDP socket #3, dnscrypt-proxy.socket, [::1]:5454 Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Source [relays] loaded Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Source [odoh] loaded Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Source [public-resolvers] loaded Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Loading the set of allowed names from [allowed-names] Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Firefox workaround initialized Jun 7 23:56:47 droid dnscrypt-proxy[877]: [2021-06-07 23:56:47] [NOTICE] Loading the set of blocking rules from [blocked-names] Jun 7 23:56:49 droid dnscrypt-proxy[877]: [2021-06-07 23:56:49] [ERROR] [odoh-crypto-sx] does not have an ODoH configuration Jun 7 23:56:49 droid dnscrypt-proxy[877]: [2021-06-07 23:56:49] [NOTICE] dnscrypt-proxy is waiting for at least one server to be reachable

jedisct1 commented 3 years ago

What relay are you using for it?

jedisct1 commented 3 years ago

Also, can you run a -short-certs to check that you don't get a different cert than I do for the relay?

syphyr commented 3 years ago

I'm not using it as a relay. I thought this was a server. When I use -show-certs, this is the results:

[2021-06-08 00:26:54] [NOTICE] dnscrypt-proxy 2.0.46-beta1 [2021-06-08 00:26:54] [NOTICE] Source [public-resolvers] loaded [2021-06-08 00:26:54] [NOTICE] Source [relays] loaded [2021-06-08 00:26:54] [NOTICE] Source [odoh] loaded [2021-06-08 00:26:54] [NOTICE] Loading the set of allowed names from [allowed-names] [2021-06-08 00:26:54] [NOTICE] Firefox workaround initialized [2021-06-08 00:26:54] [NOTICE] Loading the set of blocking rules from [blocked-names]

syphyr commented 3 years ago

I am testing it like this: server_names = ['odoh-crypto-sx']

jedisct1 commented 3 years ago

ODoH servers should be used via ODoH relays.

syphyr commented 3 years ago

odoh-cloudflare works fine without a relay defined.

jedisct1 commented 3 years ago

Note to self: output a hard error when an ODoH server is configured without a relay.

I thought it would be a useful feature for debugging your own ODoH server, but this is going to be a support hell.

syphyr commented 3 years ago

odoh-crypto-sx is still not working, even with a relay configured. Although, odoh-cloudflare is working with relay now as well.