AdguardTeam / AdguardTeam/AdGuardHome
Dynamic HTTPS record rewrite with $dnsrewrite (CNAME flattening) not working
- 主要言語
- TypeScript
- スター
- 36.9k
- フォーク
- 2.5k
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
### 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
Related and solved: https://github.com/AdguardTeam/AdGuardHome/issues/8276
Software version: adguardhome v0.107.78 and chrome 150.
I want to overwrite the HTTPS record of domain A with the dynamically fetched HTTPS record of domain B with `$dnsrewrite`. I do that with a CNAME record and it doesn't work in chrome.
Steps to reproduce:
- add adguardhome rules, `||what.a.ever^$dnstype=HTTPS,dnsrewrite=NOERROR;CNAME;what.b.ever`.
- check the HTTPS record of `what.a.ever` with an dns query utility, e.g. https://github.com/natesales/q, it returns both CNAME `what.b.ever` and HTTPS record from `what.b.ever`.
- access `https://what.a.ever` in chrome, and with the correct HTTPS record, ECH should be enabled, but is disabled.
### Proposed solution
When querying HTTPS record from AdGuardHome, it should emphasize HTTPS record instead of CNAME record.
### Alternatives considered and additional information
There are several domains for ECH testing, e.g.
- https://defo.ie/ech-check.php
- https://crypto.cloudflare.com/cdn-cgi/trace
- https://tls-ech.dev
コントリビューションガイド
評価
この issue はまだ評価されていません。