Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Malformed Response on all relays since 22/09/16 5pm CEST #737

Closed
logopk opened this issue Sep 17, 2022 · 6 comments
Closed

Malformed Response on all relays since 22/09/16 5pm CEST #737

logopk opened this issue Sep 17, 2022 · 6 comments

Comments

@logopk
Copy link

logopk commented Sep 17, 2022

Hi, I'm facing a problem with resolution.

[2022-09-17 14:00:18] [ERROR] No valid network configuration for [odoh-cloudflare]
[2022-09-17 14:00:18] [NOTICE] dnscrypt-proxy is waiting for at least one server to be reachable
[2022-09-17 14:00:28] [NOTICE] Anonymizing queries for [odoh-crypto-sx] via [odohrelay-crypto-sx]
[2022-09-17 14:00:29] [WARNING] Unable to decrypt response from [odoh-crypto-sx]: [Malformed response]
[2022-09-17 14:00:29] [INFO] Trying to fetch the [odoh-crypto-sx] configuration again
[2022-09-17 14:00:29] [NOTICE] Anonymizing queries for [odoh-crypto-sx] via [odohrelay-crypto-sx]
[2022-09-17 14:00:31] [WARNING] Unable to decrypt response from [odoh-crypto-sx]: [Malformed response]

All of a sudden I had no DNS anymore. Fortunately I was able to connect my pihole to cloudflared (config from some time ago)

I have no idea how to troubleshoot. What info do you need - or maybe you immediately know the problem?! log_level does not get more output.

I can tell from the mtail logs (and my prometheus exporter) that it started with a NETWORK_ERROR and since then I get only NOT_READY response codes.

Thanks in advance

Peter

@ecliptik
Copy link

I had the same issue with the odohrelay-crypto-sx relay.

Switching to a different relay[1] and resolver[2] resolved the issue. I don't understand why odohrelay-crypto-sx suddenly started giving [Malformed response] message though.

  1. https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/odoh-relays.md
  2. https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/odoh-servers.md

@logopk
Copy link
Author

logopk commented Sep 17, 2022

How can I force dnscrypt-proxy to use another relay - the file is loaded from github and odohrelay-crypto-sx is #1...

@logopk
Copy link
Author

logopk commented Sep 17, 2022

How can I force dnscrypt-proxy to use another relay - the file is loaded from github and odohrelay-crypto-sx is #1...

routes = [
{ server_name='*', via=['odohrelay-crypto-sx', ''] }
]
????

@logopk
Copy link
Author

logopk commented Sep 17, 2022

routes = [ { server_name='*', via=['odohrelay-ibksturm', ''] } ] did the trick.

Is there a way to get this resolved automagically? Just in case ibksturm fails one day?

@ibksturm
Copy link
Contributor

ibksturm commented Sep 17, 2022

try this

routes = [ { server_name='*', via=['odohrelay-ibksturm', 'server2‘, ‘server3‘] } ]

watchup: i write with iphone, maybe the ‘ are the wring signens

@jedisct1
Copy link
Member

This is due to a regression in zig when using the stage2 compiler.

A new version of the odoh-crypto-sx code compiled with the previous (stage1) compiler has been deployed, and the relay should be up and running again.

Thanks!

@DNSCrypt DNSCrypt locked and limited conversation to collaborators Oct 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants