DNSCrypt newest version not working?

[m00nbl00d]

Originally Posted by funkydude

I don't see how, also according to the status page it's been under maintenance for several days, this only started today. If it was a server issue it should re-direct.

edit: server side issue they are (hopefully) fixing https://github.com/opendns/dnscrypt-proxy/issues/24

Damn... the problem still isn't solved? The newest version still fails to retrieve the certificates from the server. I'm using an older version for the meantime.

I hope they fix it ASAP.

[m00nbl00d]

By the way, you can still use the latest version, but for the meantime you'll have to force it to use port 53, as it uses 443 by default. The parameter to be used is --resolver-port=53.

[funkydude]

Originally Posted by m00nbl00d

By the way, you can still use the latest version, but for the meantime you'll have to force it to use port 53, as it uses 443 by default. The parameter to be used is --resolver-port=53.

Added it to the scheduled task launch options and now it works, thanks!

[funkydude]

Apparently it's already been fixed (server-side). Removed the extra argument and rebooted for good measure, working fine on port 443 again.

In other news the proxy has been updated again, this time to 1.0, guess I'll try it out.

[m00nbl00d]

Originally Posted by funkydude

Apparently it's already been fixed (server-side). Removed the extra argument and rebooted for good measure, working fine on port 443 again.

In other news the proxy has been updated again, this time to 1.0, guess I'll try it out.

Thanks for the heads up! About time, I must say.

[m00nbl00d]

So, it wasn't the upgrade to DNSCrypt that made my PowerShell script go crazy; it actually was the fact I had installed .NET Framework v4. PowerShell v2 works with .NET Framework v2, so everything got screwed.

Anyway, it's working now, and it actually gave the chance to improve the script.

[learningcurve]

Originally Posted by jedisct1

Hi,

If you are having issue with dnscrypt, please open a ticket on Github instead.

Old versions used UDP port 53 by default. But since a lot of routers and ISPs are hijacking this, recent versions use port 443 by default, but still over UDP. So you need to open that on your firewall.

If you need to use port 53, you can always start dnscrypt with --resolver-port=53. And if you absolutely need to always use TCP, which is a terrible idea, add --tcp-only.

I really need help with DNScrypt. Now trying to use Proxy ver 1.0.1.

I only have outbound request, no reply:
xxxx.xxx.xxx.xxx 208.67.220.220 UDP Source port: 62991 Destination port: https 62991 443

Previously, have tried v.0.5 release with KIS 2012 -- only tcp:443 seemed to work. Even when I tweaked the KIS firewall rules. Then tried win7 firewall (w/default deny) and had several days of DNScrypt using port 53 properly. Then that stopped, no idea why. I then forced tcp;443. That worked for few days. Then nothing.

firewall rules for KIS
(127.0.0.1 is set on NIC)
Allow UDP outbound stream from 443, 53 (ip 208.67.220.220)
Allow UDP inbound stream from 443 (ip 208.67.220.220)
(KIS has it's preset UDP DNS firewall rule --presumably geared toward 53 only, and I have it enabled but rules listed are *above* regular DNS rule).

Troubleshooting I actually got the proxy to initiate once or twice, a reply from opendns. I think it had switched to port 53 after authentication, but *then* no dns requests could be made. Weird.

What am I doing wrong? Grateful for any help.