hi there, crew operates a free, independent "network" of 21 DNSCrypt servers spread across the globe to keep your surfing safe and secure.
Welcome and enjoy the world where we take care about Your digital footprint and data anonymity as much as You're allowing us by Your online habbits. At the end of a day it's ONLY up to You what's revealed/shared and go out of Your control. It's ONLY Your decision, thanks to our technology, countless experience and knowledge. It's all ONLY up to You with dns4.cc DNS servers.
"Freedom is like the future. We all deserve it, but we have to want it to come to us."*
* citation by darkmark, feel free to use & spread it!:)
🆕 Ladies and gentlemen, good NEWS! 🆕
Dec-16-2024 dns4.cc-de-* in 🇩🇪 is back!
Dec-13-2024 - Let us kindly introduce the new node in 🇸🇬! We add new node in Singapore, it's in beta regime now, but feel free to test it! It runs on OVH cloud and its names are dns4.cc-sg-ipv4, dns4.cc-sg-ipv6, anon-dns4.cc-sg-ipv4 and anon-dns4.cc-sg-ipv6. Enjoy the new node in an Asian business capital and let us know your experiences.
Sep-7-2024 - Big in 🇯🇵, great song by Alphaville, I'm wondering if you remember how great this song by Alphaville was. We were teenagers then, but now it's going to be true! dns4.cc crew will soon introduce new dns4.cc-jp-ipv4 & dns4.cc-jp-ipv6 nodes. It's located near the holy Mt. Fuji, which is a very special place. Check the map, circle around the globe then closes. Expected launch date in September 2024.
Jun-1-2024 - We're thrilled to announce that dns4.cc-cz is back and better than ever! Thanks to our friends in Prague 🇨🇿, we've reincarnated dns4.cc-cz & anon-dns4.cc-cz! It's finally back, and it's better, cooler, and stronger than ever. Now it supports both IPv4 and IPv6, and it's in beta mode. We'd love for you to test it as much as possible to prove connectivity and stability.
A big thank you to Marek (he knows...) for handling the negotiations, translating, and being so welcoming. We had the most incredible, unforgettable couple of days in the most beautiful, ancient city of Prague... 🍺🍺🍺 🇨🇿 😎
Personally, we are strong believers in FREEDOM and the basic human right to remain anonymous and untraceable if you choose so.
Respecting this fact, all dns4.cc resolvers & anonymizing relays were, are, and always will be:
- PUBLIC & FREE TO USE
- SECURED BY DNSSEC
- NON-BLOCKING
- NON-LOGGING
- NON-FILTERED
All servers would be used as DNSCrypt public resolvers and/or anonymizing relays.
We mainly use GreenCloud vps for their affordability, great support and open minded approach, use our referral link to give them a try.
Before we get started, it's nice to keep in mind a few really basic reminders about how to behave in a binary world:
- It's OK to be suspicious, suspicious and one more time suspicious and cautious in every way possible.
- It's okay to use only proven tools or software (I don't want to push you into a corner, but DNS servers provided by dns4.cc are the best choice 😆).
- It's normal to consider your data and digital security and/or anonymity as a treasure.
- ACABs(👮), 🕵️, hackers, 🤖 and other whatever suckers never sleep and are at least one step ahead...
- This fight should NEVER be over.
- It's generally getting worse by the minute.
- At the end of the day, you're the only one responsible for your digital anonymity and security.
And finally how to 🏁
To start using our network simply add the lists of dns4.cc servers and anonymization relays to your dnscrypt-proxy.toml config, restart the service and enjoy.
Right, we boldly assume that you already have dnscrypt-proxy installed on your 💻 and/or 📱. 😉 If not, visit the dnscrypt-proxy repo for more details and return back when you are done. Theory and other useful stuff can be found at the DNSCrypt website.
It's easy as:
- Either download dns4.cc repository as ZIP or clone it to anywhere like:
git clone https://github.com/drkmark/dns4.cc.git
and copy all the files to dnscrypt-proxy working directory (i.e. /opt/dnscrypt-proxy/)
-
In
[sources]section of yourdnscrypt-proxy.tomlconfiguration file you should add something like:a. dns4.cc public resolvers
[sources.'dns4.cc-resolvers.md'] urls = ['https://raw.githubusercontent.com/drkmark/dns4.cc/main/dns4.cc-resolvers.md'] cache_file = 'dns4.cc-resolvers.md' minisign_key = 'OUR-PUBLIC-MINISIGN-KEY-GOES-HERE' refresh_delay = 72b. dns4.cc anonymizing relays
[sources.'dns4.cc-relays.md'] urls = ['https://raw.githubusercontent.com/drkmark/dns4.cc/main/dns4.cc-relays.md'] cache_file = 'dns4.cc-relays.md' minisign_key = 'OUR-PUBLIC-MINISIGN-KEY-GOES-HERE' refresh_delay = 72 -
In
[anonymized_dns]section then add routes as needed, i.e. (or as you wish):routes = [ { server_name='dns4.cc-us-ca-ipv4', via=['anon-dns4.cc-us-ny-ipv4'], via=['anon-dns4.cc-us-tx-ipv4'] }, { server_name='dns4.cc-vn-ipv6', via=['anon-dns4.cc-hk-ipv6'], via=['anon-dns4.cz-ipv6'] }, ..... ]
Btw. it's not necessary to be "superanonymized" over more than 1-2 relays, as the latency would increase dramatically. Just check and play with routes to test the latency, e.g. with DNS leak script from @macvk.
Read "/your/dncrypt-proxy/working-directory/"example-dnscrypt-proxy.toml for proper settings!
DNS servers locations as of December 2024:
- San Jose, CA
- Dallas, TX
- Buffalo, NY
- Coventry, UK 🇬🇧
- Frankfurt Am Main, Germany 🇩🇪
- Budweis, Czechia 🇨🇿
- Bratislava, Slovakia 🇸🇰
- Ho Chi Minh City, Vietnam 🇻🇳
- Hong Kong, China 🇨🇳
- Tokyo, Japan 🇯🇵
- Singapore 🇸🇬
...and that's all, folks. have a good time!
©2024 darkmark & dns4.cc crew