Repository navigation
Router: domain and TLS certificate requirements #8635
|
Hello, |
Replies: 2 comments 18 replies
|
There are two different "encrypted DNS" directions, and only one of them needs a domain and certificate.
Supported formats are listed here: https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration#upstreams So yes, you can skip the Encryption settings entirely. Devices on your LAN keep using the router as plain DNS (that traffic never leaves your home), and AdGuard Home encrypts everything it sends out to the internet. The public services you are comparing with already have their own domain and certificate, which is why you never had to provide one there. |
|
Thank you very much for your detailed reply. I had misunderstood what encrypted DNS meant. Glinet is now showing me that I am using the DoT and DoH servers I selected on adguard home. My final question is: how can I actually check whether I am really using these DNS servers, or whether a fallback is being used instead? |
There are two different "encrypted DNS" directions, and only one of them needs a domain and certificate.
AdGuard Home acting as an encrypted DNS server (Settings > Encryption settings). Here your devices connect to AdGuard Home over DoH/DoT/DoQ. Those protocols run on TLS, so the server has to present a certificate that matches a name the clients connect to, the same way any HTTPS website does. That is why it asks for a domain and a cert (Let's Encrypt works fine). The wiki also notes it does not make much sense to set this up only for your own LAN, it is mainly for using your AdGuard Home from outside your network: https://github.com/AdguardTeam/AdGuardHome/wiki/Encryption
AdGuard Ho…