AdguardTeam / AdguardTeam/AdGuardHome
Option to add disallowed domains option per client
- Vorherrschende Sprache
- TypeScript
- Sterne
- 36.9k
- Forks
- 2.5k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Have a question or an idea? Please search it [on our forum](https://github.com/AdguardTeam/AdGuardHome/discussions) to make sure it was not yet asked. If you cannot find what you had in mind, please [submit it here](https://github.com/AdguardTeam/AdGuardHome/discussions/new).
### Prerequisites
Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.**
- [x] I am running the latest version
- [x] I checked the documentation and found no answer
- [x] I checked to make sure that this issue has not already been filed
### Problem Description
Disallowed domain option in DNS Settings —> Access Settings is a very useful feature to hide noisy DNS requests spamming the DNS log. Currently no support to **_define disallowed domains per client_**. However this feature can be super useful. For example, some of my IoT devices query google.com every interval of seconds. I can block google.com for the specific client but that blocking still flood the blocked domains statistics. Clearly I can not simply add google.com to disallowed domain as other clients need access to that domain.
### Proposed Solution
Please consider adding option of disallowed domains option per client, in similar syntax as blocked domains per client
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.