wg-access-server VS AdGuardHome

I tried them all. I settled on wg-access-server.

Yes, at my startup we run https://github.com/Place1/wg-access-server inside our kubernetes clusters to give engineers access to local pods vs the k8s DNS (.svc.cluster.local). It works relatively well but we've had to make a couple modifications:

1. I had to deploy CoreDNS to our cluster and set up DNS query rewriting to redirect queries from .cluster.mystartup to *.svc.cluster.local because docker on OS X has issues resolving hostnames that end in .local

What is the difference from https://github.com/Place1/wg-access-server ?

Not sure why this is downvoted. I use a similar service that runs in docker just fine. https://github.com/Place1/wg-access-server

Also AdGuardhome will use optimistic caching, which is great.

https://github.com/AdguardTeam/AdGuardHome/discussions/4002#...

The main repo is GPLv3: https://github.com/AdguardTeam/AdGuardHome

They already have many other commercials products and I guess also the default filter rules are very good because of their experience in the domain.

But I think you can use it completely without the AdGuard servers and use other filter list sources.

How it compares to let's say AdGuard Home? Seems similar https://github.com/AdguardTeam/AdGuardHome

Adguardhome - Clients identification issue

You can check this documentation if you want to investigate further: https://github.com/AdguardTeam/AdGuardHome/wiki/Hosts-Blocklists

I'm using adguardhome v0.107.42 openwrt snapshot on linksys wrt1900ac v2, but when using DoH it won't resolve upstream DNS, but DoT is works perfectly OK, I've already set allow_unencrypted_doh to true in config .yaml file as per instruction here

AdGuard Home?

https://github.com/AdguardTeam/AdGuardHome

Regarding open source, AdGuard DNS actually is:

How does this compare to adguard home [ https://github.com/AdguardTeam/AdguardHome ] ??

Have you looked at AdGuard Home - Configuring clients?