# Containers unable to reach external url's because of self signed certificates **URL:** \ **Category:** General Discussions\ **Created:** [April 28, 2022, 9:03am UTC](https://discuss.kubernetes.io/t/containers-unable-to-reach-external-urls-because-of-self-signed-certificates/19809 "2022-04-28T09:03:57Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![nicky](https://avatars.discourse-cdn.com/v4/letter/n/f0a364/32.png) [@nicky](https://discuss.kubernetes.io/u/nicky)\ **Post date:** [April 28, 2022, 9:03am UTC](https://discuss.kubernetes.io/t/containers-unable-to-reach-external-urls-because-of-self-signed-certificates/19809/1 "2022-04-28T09:03:57Z")
### Cluster information: Kubernetes version: 1.23.6 Cloud being used: Bare Metal Installation method: Package Manager Host OS: Debian 11 CNI and version: Calico 3.22.2 CRI and version: Containerd 1.4.13 I’m working on a manifest that allows me to deploy a matrix synapse server in a kubernetes cluster, but I’m running across the issue that whenever a container tries to access a url over https, the SSL certificate that gets returned is that of my pfSense box. This happens on all of my running pods, not only on my matrix deployment. This then causes self signed certificate errors in matrix (and other applications). ---
**Author:** ![nicky](https://avatars.discourse-cdn.com/v4/letter/n/f0a364/32.png) [@nicky](https://discuss.kubernetes.io/u/nicky)\ **Post date:** [April 28, 2022, 12:52pm UTC](https://discuss.kubernetes.io/t/containers-unable-to-reach-external-urls-because-of-self-signed-certificates/19809/2 "2022-04-28T12:52:47Z")
After messing around in the container, I found out that whenever my containers make a dns querry, my domain gets appended to it. So [google.com](http://google.com) becomes [google.com.mydomain.com](http://google.com.mydomain.com). Anyone got an idea as to why this is happening?