* In environments where DNS resolution is not yet available at the time RabbitMQ nodes boot and try to perform [peer discovery](https://www.rabbitmq.com/cluster-formation.html),
such as CoreDNS with default caching interval of 30s on Kubernetes, nodes now will retry
hostname resolution (including of their own host) several times with a wait interval.
The recommended solution is to [decrease CoreDNS caching interval](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#stable-network-id).
* Three more security-related response headers now can be set for all HTTP API endpoints:
*`X-Frame-Options`
*`X-Xss-Protection`
*`X-Content-Type-Options`
``` ini
management.headers.content_type_options = nosniff
management.headers.xss_protection = 1; mode=block
management.headers.frame_options = DENY
```
This is in addition to the [CSP](https://www.rabbitmq.com/management.html#csp), [HSTS](https://www.rabbitmq.com/management.html#hsts), and [CORS](https://www.rabbitmq.com/management.html#cors) headers: