Best practices for setting up a new router: single vs multi-band SSID & firewall security level?
- Thread starter lokamoka820
- Start date
Please provide comments and solutions that are helpful to the author of this topic.
For Zero Trust, you need to use Cloudflare One app. Currently the situation is messy. On Windows, there's Cloudflare One app for WARP and Zero Trust. On Android, WARP and Zero Trust have different apps (1.1.1.1 for WARP, Cloudflare One for Zero Trust).Is the Zero Trust client app a different app from WARP?
Also, MASQUE is Cloudflare developed protocol that is faster than Wireguard. If you're planning to use their app, make sure MASQUE protocol is chosen in the dashboard.
Last edited:
It connects fine for me. That's how I have been using for a long time. Not sure what's wrong on your end
Maybe conflict with something else? Just now I even tried it on the WireGuard Android app and it works here also. It's also not necessary to replace the engage cloudflare domain to an IP for this.
Did the logs show any errors on your side? On my end, errors still appear, but everything works as expected with no slowdowns or false positives.I set log to errors only now, we'll see how much errors I get surfing the web.
I'm currently not using YogaDNS as I'm testing DoH support built-in Windows, but yeah, I too sometimes get errors with QUIC and DoH3.
If everything is working correctly for you, no reason to panic. What DNS are you using now? Did you stick with Control D, Cloudflare or something else?
Last edited:
I first switched to AdGuard Home as SeriousHoax recommended, adding all the DNS filters I had tested in YogaDNS along with Cloudflare Zero Trust DNS to compare their speeds simultaneously. I used the AdGuard DNS filter and Hagezi Pro as block lists, and everything worked as expected. However, I noticed that Control D was generally about 5ms slower than Cloudflare from my location, based on AdGuard Home's 24-hour reports. Consequently, I switched back to using Control D with Hagezi Pro DNS through YogaDNS. I may eventually move to Windows built-in settings once the YogaDNS trial period ends.What DNS are you using now? Did you stick with Control D, Cloudflare or something else?
Did Control D support ever got back to your regarding routing?
I think I'll keep using Windows built-in setting because now I have the option not to fallback to plain DNS. I only installed YogaDNS because I haven't had that option available in settings at all.
No, they don't, but I'm glad I don't notice any slowdowns during my daily browsing.
I'm considering using Windows' built-in settings as well, but for third-party software, I think I'll go with AdGuard Home—the option to configure multiple DNS servers in parallel is brilliant.
I like AdGuard Home, but I wish it was more of an app for Windows, not same variant like for the server.
I found an alternative called "Technitium DNS Server". Have you tried it?
Nah. I don't need it. Windows built-in DoH is enough for me. Keep in mind using software to create local DNS server on your PC only increases CPU usage because your PC has to resolve all the requested domains AND search them in the blocklists you chose.
In NextDNS case, maybe very little? Or, am I off track for where the conversation was?
He is referring to DNS servers rather than DNS clients, so NextDNS and YogaDNS are not affected by this issue.
What I'm talking about are apps/programs like Pi-Hole, AdGuard Home running on the PC rather than server. They create local DNS server on device with blocklists you choose; basically local instance of NextDNS for that one device.
When you do this, all the DNS traffic and searching the added blocklists is done on the PC itself, meaning it uses CPU. When you're using NextDNS, Control D or any other similar service, you're not using any CPU because that job is done by their servers.
Now, I don't know about you guys, but if I can offload some work to servers, I will. Less CPU used, the more of it available for other, more important jobs. This then translates to better/longer battery life. I stopped using AdGuard for Android for that particular reason. No need for app to filter apps traffic when DNS can do it as well. Since AdGuard can't do cosmetic filtering in apps and can only block connection to ad server, it's no different than the ad blocking DNS.
Last edited:
I have used it. It's much more powerful than AdGuard Home, as it's a full-blown DNS server. It can be used as a recursive DNS resolver, which is its default, but it can be used as a forwarder, similar to AdGuard Home.
It has plenty of features and is an amazing piece of software, but it's usually too much for a personal PC. It is more useful to use it on a separate dedicated hardware, which is for example, is your home's primary DNS.
People use it in their companies or private institutions as their recursive DNS resolver, resolving millions of queries every day.
I used it on my PC too, where it was mostly helpful to me to pass certain domains to be resolved by my router's WireGuard VPN instead of going through my ISP, as well as prefetching DNS and serving stale cache.
The developer is extremely helpful and always replies in detail. I initially even asked him some stupid questions (didn't realize at the time), but he never showed any annoyance and has always been very professional.
Anyway, you may try it only if you are very curious, otherwise, you won't need it.
Just to add a bit of clarity about DNS, because sometimes different concepts get mixed together.
AdGuard Home works as a local DNS server. The device itself handles the DNS requests and applies the blocklists, so it uses some CPU and memory. However, on modern home systems, the impact is usually very low. Even with large lists, in my experience, it does not cause slowdowns or noticeable performance issues.
On the other hand, NextDNS, YogaDNS, and the Windows native DNS client work as DNS clients: they simply send the requests to an external server, where filtering, caching, and security features are handled. That is why the local resource usage is usually almost negligible.
I think separating these two ideas helps explain why some users notice resource usage while others do not. In a home environment, AdGuard Home is generally a lightweight solution, while DNS clients move most of the processing to the external service.
AdGuard Home works as a local DNS server. The device itself handles the DNS requests and applies the blocklists, so it uses some CPU and memory. However, on modern home systems, the impact is usually very low. Even with large lists, in my experience, it does not cause slowdowns or noticeable performance issues.
On the other hand, NextDNS, YogaDNS, and the Windows native DNS client work as DNS clients: they simply send the requests to an external server, where filtering, caching, and security features are handled. That is why the local resource usage is usually almost negligible.
I think separating these two ideas helps explain why some users notice resource usage while others do not. In a home environment, AdGuard Home is generally a lightweight solution, while DNS clients move most of the processing to the external service.
You may also like...
-
Harden Windows Security | Only with official documented methods | Always up to date- Started by SpyNetGirl
- Replies: 76
-
-
H