To visually interact with dnsdist, try add
webserver to the configuration:
Now point your browser at http://127.0.0.1:8083 and log in with any username, and that password. Enjoy!
The built-in webserver serves its content from inside the binary, this means it will not and connot read from disk.
By default, our web server sends some security-related headers:
X-Content-Type-Options: nosniff X-Frame-Options: deny X-Permitted-Cross-Domain-Policies: none X-XSS-Protection: 1; mode=block Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'
You can override those headers, or add custom headers by using the last parameter to
webserver. For example, to remove the X-Frame-Options header and add a X-Custom one:
Credentials can be changed over time using the
To access the API, the apikey must be set in the
webserver function. Use the API, this key will need to be sent to dnsdist in the
X-API-Key request header. An HTTP 401 response is returned when a wrong or no API key is received. A 404 response is generated is the requested endpoint does not exist. And a 405 response is returned when the HTTP methos is not allowed.