Description
It would be very useful if RouteDNS could support Proxy Protocol (both v1 and v2). This feature is important for deployments behind load balancers or reverse proxies where preserving the original client IP is required.
Use Case
When RouteDNS is deployed behind a proxy (e.g., HAProxy, NGINX, or cloud load balancers), the real client IP is lost. Supporting Proxy Protocol would allow RouteDNS to correctly identify and log the original source IP of incoming DNS queries.
Proposed Solution
• Add support for parsing Proxy Protocol headers (v1 and v2) on incoming connections.
• Optionally allow enabling/disabling this feature via configuration.
• Ensure compatibility with both TCP and TLS listeners if applicable.
Benefits
• Accurate client IP logging
• Better integration with modern infrastructure setups
• Improved observability and debugging
Additional Context
Many DNS services and network tools already support Proxy Protocol, and adding this would make RouteDNS more flexible in production environments.
References
• Proxy Protocol specification: https://www.haproxy.org/download/2.0/doc/proxy-protocol.txt
Thank you
Description
It would be very useful if RouteDNS could support Proxy Protocol (both v1 and v2). This feature is important for deployments behind load balancers or reverse proxies where preserving the original client IP is required.
Use Case
When RouteDNS is deployed behind a proxy (e.g., HAProxy, NGINX, or cloud load balancers), the real client IP is lost. Supporting Proxy Protocol would allow RouteDNS to correctly identify and log the original source IP of incoming DNS queries.
Proposed Solution
• Add support for parsing Proxy Protocol headers (v1 and v2) on incoming connections.
• Optionally allow enabling/disabling this feature via configuration.
• Ensure compatibility with both TCP and TLS listeners if applicable.
Benefits
• Accurate client IP logging
• Better integration with modern infrastructure setups
• Improved observability and debugging
Additional Context
Many DNS services and network tools already support Proxy Protocol, and adding this would make RouteDNS more flexible in production environments.
References
• Proxy Protocol specification: https://www.haproxy.org/download/2.0/doc/proxy-protocol.txt
Thank you