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
Program: Authoritative (at least, but might also be in Recursor, dnsdist)
Issue type: Feature request
Short description
When the PowerDNS Webserver is behind a proxy (e.g. nginx) and the proxy alters the headers to set x-forwarded-for or x-real-ip the PowerDNS Webserver ignores this, and shows the IP of the Proxy (in my case a local docker container IP)
This makes it hard to see who is using the webserver
Short description
When the PowerDNS Webserver is behind a proxy (e.g. nginx) and the proxy alters the headers to set x-forwarded-for or x-real-ip the PowerDNS Webserver ignores this, and shows the IP of the Proxy (in my case a local docker container IP)
This makes it hard to see who is using the webserver
Usecase
making the logging more acurate.
Description
Just use x-forwarded-for or x-real-ip as the client ip when they are set. Even better would be if there was a option to tell the PowerDNS Webserver wich ip is trusted to set x-forwarded-for
( https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html#remoteipinternalproxy )
The text was updated successfully, but these errors were encountered: