the server doesn't change, it is SimpleDNS that redirect your DNS adress to localhost (to itself in fact) , that allows you to use its features.
Disable one of the 2 button in simpleDNS then enter manually the wanted DNS in the protocol tabs.
The associated guide may contain user-generated or external content.
the server doesn't change, it is SimpleDNS that redirect your DNS adress to localhost (to itself in fact) , that allows you to use its features.
Disable one of the 2 button in simpleDNS then enter manually the wanted DNS in the protocol tabs.
- Feb 22, 2013
- 451
Thanks you Umbra for sharing,interesting reading.
Hi Umbra
If I choose a DNSCrypt server which supports DNSSEC validation it means I'm getting the best of both encryption and validation of the DNS query/response from the server, right?
Thanks
If I choose a DNSCrypt server which supports DNSSEC validation it means I'm getting the best of both encryption and validation of the DNS query/response from the server, right?
Thanks
Last edited:
Hi
Simple DNSCrypt v0.3.9 just released and I got it updated. A message prompts the update and you just acknowledged the update.
Changelog
What's new in Simple DNSCrypt 0.3.9
January 4th, 2017
Simple DNSCrypt v0.3.9 just released and I got it updated. A message prompts the update and you just acknowledged the update.
Changelog
What's new in Simple DNSCrypt 0.3.9
January 4th, 2017
- Fix resolver update button
- Switch to .NET 4.6 (the block list now can download remote files with TLS 1.2)
- Support DNSCrypt v2 on certificate validation (analyse button)
- Remove failed resolvers from the list (analyse button)
Last edited:
Simple DNSCrypt just released its v0.4.0
What's new in Simple DNSCrypt 0.4.0
January 5th, 2017
What's new in Simple DNSCrypt 0.4.0
January 5th, 2017
- Added Tab: Live Log (watch the dns log within Simple DNSCrypt) Fixes #39.
- Added Persian/Farsi translation (@robin98)
- Updated Spanish translation (@pablomh)
- Dec 25, 2016
- 21
Hi - Looking for some assistance please.. Simple DNSCrypt updated itself a couple days ago and I can't get it to work. After the update I went to dnsleaktest and noticed it was not showing the resolvers I selected, as it previously did, but showing some OPEN DNS servers. I think the reason for that is because I changed my secondary dns to an Open DNS server..
So I reinstalled, selected my network card and resolvers, turned on the service, verified it had changed my dns servers to 127.0.0.1 and 127.0.0.2 but I lost all internet access.
I hope there is something "simple" I'm missing.. as I usually overlook minor details.. and networking stuff is not something I'm good at.
Thanks!
So I reinstalled, selected my network card and resolvers, turned on the service, verified it had changed my dns servers to 127.0.0.1 and 127.0.0.2 but I lost all internet access.
I hope there is something "simple" I'm missing.. as I usually overlook minor details.. and networking stuff is not something I'm good at.
Thanks!
Report it to the developer (bitbeans) on GitHub. There have been a lot of problems with Simple DNSCrypt as of late.
Last edited by a moderator:
- Dec 25, 2016
- 21
Thanks.. took a minute to find the discussion link.. looks like it is most likely a problem with my Kaspersky (which I'm learning has a lot of compatibility issues)
FYI, no problem on my side. No Kaspersky for me.
There have been a lot of problems with Simple DNSCrypt on W10 lately; cannot connect to DNS server, will not uninstall completely, will not reset network settings to default upon uninstall,...
It is best to report it to bitbeans.
Isn't that wonderful for you.
So far okay. Running on Win 10 Pro 64-bit
- Jun 10, 2014
- 316
There's definite problems with SDNSC on W10.
The more people that report their issues to bitbeans, the sooner he will get them fixed.
Few people bother to report issues. If bitbeans doesn't know about them, then he ain't gonna fix them. On top of it he's busy, so it's not like he's on GitHub every single day.
The more people that report their issues to bitbeans, the sooner he will get them fixed.
Few people bother to report issues. If bitbeans doesn't know about them, then he ain't gonna fix them. On top of it he's busy, so it's not like he's on GitHub every single day.
Ok v0.4.1 is under preparation
GitHub - bitbeans/SimpleDnsCrypt: A simple management tool for dnscrypt-proxy
Bitbeans has accepted my reports and classified as BUG.
Simple DNSCrypt just released its v0.4.1
Simple DNSCrypt - Official Project Home Page
Just got mine updated
Simple DNSCrypt - Official Project Home Page
Just got mine updated
HarborFront Thank you! Just updated.
Why did SimpleDnsCrypt get rid of the Cryptostorm DNS servers? They are not available anymore.
Why did SimpleDnsCrypt get rid of the Cryptostorm DNS servers? They are not available anymore.
What's new in Simple DNSCrypt 0.4.1
January 22nd, 2017
January 22nd, 2017
- Updated dnscrypt-proxy to 1.9.3
- Updated dnscrypt-resolver.csv
- Include Universal C Runtime DLLs (KB2999226)
- Updated Spanish translation (@pablomh)
- Updated French translation (@didihu)
- Updated Indonesian translation (@christantoan)
- Updated Swedish translation (@eson57)
- Updated Russian translation (Vlad)
- Updated Uninstall.exe (clear network cards)
- Fixed the update check (there are now UnitTests!)
- Note: There was a bug in the update parser (0.3.9 and 0.4.0). So maybe you need to download this release manually. Sorry!
What's new in Simple DNSCrypt 0.4.2
March 4th, 2017
March 4th, 2017
- Updated dnscrypt-proxy to 1.9.4
- Updated dnscrypt-resolver.csv
- Updated Chinese translation (@jerryhou85)
- Added Bulgarian translation (@rddim)
- Updated dependencies
Similar threads
