Suraj Nath

@HamidEDD I tested ` volume.compute.bhs5.cloud.ovh.net` on ssllabs.com ([see results](https://www.ssllabs.com/ssltest/analyze.html?d=volume.compute.bhs5.cloud.ovh.net)), and it shows an expired certificate under Additional Certificates. same is true for `workflow.bhs5.cloud.ovh.net` ([test results](https://www.ssllabs.com/ssltest/analyze.html?d=workflow.bhs5.cloud.ovh.net)), and `cloudformation.bhs5.cloud.ovh.net` ([test results](https://www.ssllabs.com/ssltest/analyze.html?d=cloudformation.bhs5.cloud.ovh.net))

@Sunny-2772 can you test your targets using [ssllabs.com SSL server test](https://www.ssllabs.com/ssltest/index.html) and share results with us?

closing this, this was fixed in https://github.com/prometheus/common/releases/tag/v0.36.0. we are at `github.com/prometheus/common:v0.37.0` in black box exporter.

@mdisibio can this be closed?

going to close this, if you think this is not done. please reopen.

We managed to fix these errors with #1632, and tempo pods DNS `ndots=3` In #1632, We increased MaxIdleConns and MaxIdleConnsPerHost for Azure backend to 100 (default is 2) Testing was...

Another way to solve this without modifying `ndots` is to add `.` at then end of hostname to make the hostname fully qualified. If we go with that route, we...

In our case, we were seeing these errors only in compactor pods, so we added `ndots=3` in compactor pods for Azure. We did this by setting compactor [Pod's DNS Config](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config)...

**Update from Azure support:** Host headers are not allowed to have trailing dot in Azure services, you can use FQDN but need to set Host header without trailing dot. -...

Tested this change internally, and it has reduced errors from 4-5 errors per hour to 1 error every 2-3 hours