You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently added Proxy Protocol v2 support (for TCP/TLS) in this fork of dnsproxy, mainly to make it easier to run behind a reverse proxy or load balancer while preserving the real client IP.
A simple example setup would be:
Client → Proxy (send-proxy-v2) → dnsproxy
This works well for DoT / DoTCP and allows things like:
more accurate logging
client-based filtering / rate limiting behind a proxy
I'm trying to understand how people are actually deploying dnsproxy in the real world, especially in setups involving proxies or L4 load balancers.
A few things I'm curious about:
Are you running dnsproxy behind a proxy or LB?
Do you need real client IP, and for what purpose?
Is anyone experimenting with DNS-over-QUIC (DoQ) behind a proxy?
If you have a setup (even a simple one), I'd love to hear about it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I recently added Proxy Protocol v2 support (for TCP/TLS) in this fork of dnsproxy, mainly to make it easier to run behind a reverse proxy or load balancer while preserving the real client IP.
A simple example setup would be:
Client → Proxy (send-proxy-v2) → dnsproxy
This works well for DoT / DoTCP and allows things like:
I'm trying to understand how people are actually deploying dnsproxy in the real world, especially in setups involving proxies or L4 load balancers.
A few things I'm curious about:
If you have a setup (even a simple one), I'd love to hear about it.
Thanks!
All reactions