Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow overriding DDR response #7570

Open
3 tasks done
yegle opened this issue Jan 17, 2025 · 0 comments
Open
3 tasks done

Allow overriding DDR response #7570

yegle opened this issue Jan 17, 2025 · 0 comments

Comments

@yegle
Copy link

yegle commented Jan 17, 2025

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to request a feature or enhancement and not ask a question

The problem

I'm using Caddy reverse proxy in front of AdGuard Home so that I can restrict the access to the admin console while providing a public-accessible DNS-over-HTTPS service. Caddy also handles HTTP3/Quic on UDP port 443 which I thought is great.

But then I realized:

  1. If I set DoQ port to 443 in the settings, AdGuard will fail to start.
  2. If I do not set DoQ port to 443, then the DDR response will include a port that I do not open on my firewall:
$ kdig +short @MY-HOST +https _dns.resolver.arpa type64
1 MY-HOST. alpn=h2 port=443 key7="/dns-query{?dns}"
1 MY-HOST. alpn=doq port=784
  1. If I set DoQ port to empty string, the DDR response will omit the DoQ information:
$ kdig +short @MY-HOST +https _dns.resolver.arpa type64
1 MY-HOST. alpn=h2 port=443 key7="/dns-query{?dns}"

Proposed solution

It looks like the easiest way is to allow us to customize the DDR response, so that I can set DoQ port in the DDR response to 443.

Alternatives considered and additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant