AdguardTeam / AdguardTeam/AdGuardHome
When using multiple domains in a certificate, clientID's are recognized in only one
- Ngôn ngữ chính
- TypeScript
- Star
- 36.9k
- Fork
- 2.5k
- Chỉ số merge pull request
- Không có pull request nào được merge trong 30 ngày
Mô tả
### Prerequisites
- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions) and found no answer
- [X] I have searched other issues and found no duplicates
- [X] I want to request a feature or enhancement and not ask a question
### The problem
I created a certificate with three wildcard domains and three regular domains. The wildcard domains are in the format *.doh-agh.xxx.com, *.dot-agh.xxx.com and *.doq-agh.xxx.com.
When I enter one of these domains in the "Server Name" field on the "Encryption" tab (for example, doh-agh.xxx.com), the client IDs of the other wildcard domains are not detected. I need these additional wildcard domains to be able to route traffic in my local network differently for different DNS protocols.
### Proposed solution
I suggest adding the option to enter multiple "Server Names" in the "Encryption" tab. This way, the clientID detection will work for more than one domain.
### Alternatives considered and additional information
The reason for separating the DoH, DoT, and DoQ clients by domain is to create different paths for proxying device requests within the local network.
When I use only one domain, I have to remove the Nginx server from the request path to AdGuard Home, which disrupts the architecture of my home network.
Hướng dẫn đóng góp
Đánh giá
Issue này chưa được đánh giá.