Vault dns connection generic error during vault unseal

Hello community,

I have been setting up a dev vault configuration in a docker service. The vault service is up and running and confirming with a message in the logs that vault is running successfully

==> Vault server started! Log data will stream in below:

==> Vault server configuration:

                 Cgo: disabled
     Cluster Address:

2021/11/01 22:16:22.620807 [WARN ] physical/consul: appending trailing forward slash to path
Listener 1: tcp (addr: “”, cluster address: “”, tls: “enabled”)
Log Level: info
Mlock: supported: true, enabled: false
Redirect Address:
Storage: consul (HA available)
Version: Vault v0.7.2

And I am getting the following error when I try to unseal in the docker vault service:

Error checking seal status: Get https://“VAULT-DOMAIN-USED”:8290/v1/sys/seal-status: dial tcp: lookup “VAULT-DOMAIN-USED” on $DNS-SERVER_IP:53: no such host

After following the following steps:

#export VAULT_ADDR=https://“VAULT-DOMAIN-USED”:8290

#vault unseal

The server has connection to the internet thanks to the use of a proxy and the domain used for vault is in my dns server correctly set up.
I confirm that the vault domain is in the dns server config configured correctly.

I am perhaps missing in the vault configuration files that I should do?

Thank you for your help,

Post your actual configuration and Docker run command please.

Hello Aram,

docker run -d -p 8290:8290 -v vault_data:/tmp --name vault-test $REPOSITORY/vault $executable script (starting vault)

(The start process is successful by the way, the issue is with unseal)

About configuration as there are several config files anything in particular?


disable_mlock = true

backend “consul” {
address = “”
path = “vault”

listener “tcp” {
address = “”
tls_disable = 0
tls_cert_file = “*************”
tls_key_file = “**************”

Thank you,

You can close this issue. There was a sintax error in the dns server to solve, this fixed the issue.

Thank you for your help