AdGuard Home Wildcard aliases
-
@BrutalBirdie thank you but something is generally wrong here... wondering why there is no *.adguard.mydomain.tld but only *.mydomain.tld
...
here my Cloudron AdGuard Home App settings:
and If I try to connect via private DNS (Android) then I see this in Log-File:
[error] handling tcp: reading msg: reading len: remote error: tls: unknown certificate authority
-
@Kubernetes I want to use DoT / DoH on my Android / iOS devices and allow only my clients to use this AdGuard Home instance. I'm doing something wrong?
-
@Kubernetes But If I don't need an Alias for AdGaurd in Cloudron, how do I set the Client Identifier ind Adroids Private DNS and / or in AdGuard App? Sorry but it's confusing for me.
It this Guide https://docs.cloudron.io/apps/adguard-home/#security i need DoT for my Android devices, to an wildcard alias is needed to identify my Android devices
-
@lukas You have to set the ClientID in Adguard Home Admin Interface, but not in Cloudron. Then all you need to do is to combine the URL to your Adguard Home with the ClientID you have configured already.
This should look like this:
https://adguard.yourdomain.tld/dns-query/CLIENTIDI assume that you never had a look at the Adguard Home Admin Interface, did you? There is a tab "Setup Assistant" which explains how to do it with Android, Windows, Browser, iOS, Router....
I hope that helps?
-
@Kubernetes said in AdGuard Home Wildcard aliases:
This should look like this:
https://adguard.yourdomain.tld/dns-query/CLIENTIDyes, but for Android I have to use DoT and not DoH ?
DoT DNS over TLS (DoT) is supported and uses port 853 by default. DoT is required for Android's "Private DNS mode" (available since Android 9.0 Pie). To use Client ID identifiers, you must add a wildcard subdomain alias of the form *.adguard.domain.com.
-
@Kubernetes as I understand this, for DoT I need a wildcard domain. In AdGuard Adnroid app I can use DoH with your string, this works fine.
-
G girish moved this topic from Support on
-
@girish I switched now from Porkbun API to Wildcard Domain. How to get it working now?
Just get this:
Apr 29 22:16:09 2023/04/29 20:16:09.334842 [error] handling tcp: reading msg: reading len: remote error: tls: unknown certificate authority Apr 29 22:16:09 2023/04/29 20:16:09.584416 [error] handling tcp: reading msg: reading len: remote error: tls: unknown certificate authority Apr 29 22:16:09 2023/04/29 20:16:09.602320 [error] handling tcp: reading msg: reading len: remote error: tls: unknown certificate authority
-
@lukas Yeah, so they never got back
I even sent them a reminder. Please point them to this thread (if you are a customer). I sent mails from girish@cloudron.io
Unfortunately, one cannot create a wildcard certificate from the Wildcard Domain. This is because Let's Encrypt requires you to set values in the DNS to get a wildcard cert. With a wildcard provider, Cloudron has no way to program the DNS. Only fix right now is to switch to some other programmable DNS provider. Sorry...
-
@girish said in AdGuard Home Wildcard aliases:
Yeah, so they never got back I even sent them a reminder. Please point them to this thread (if you are a customer). I sent mails from girish@cloudron.io
you got maybe any ticket number? I will contact them now
-
@girish update to latest Cloudron Version, bunny.net integration is working fine (thanks for this), but DoT on my Android Phone is still not working, in AdGuard Home Log I see:
May 02 10:35:57 2023/05/02 08:35:57.599729 [error] handling tcp: reading msg: reading len: remote error: tls: bad certificate May 02 10:35:57 2023/05/02 08:35:57.907614 [error] handling tcp: reading msg: reading len: remote error: tls: bad certificate May 02 10:35:57 2023/05/02 08:35:57.914408 [error] handling tcp: reading msg: reading len: remote error: tls: bad certificate
What is wrong? I use <clientname>.adguard.mydomain.TLD and I added an Alias (*.adgaurd) to AdGuard Home.
What is wrong?
Thank you and Regards,
Lukas