Terraform plan fails with Error: update server is not set

[kenorb]

Terraform plan fails with Error: update server is not set

[juan-acevedo-ntt]

This keeps happening in v0.14.7 and It is a bug. If you create a dns_cname_record or a dns_a_record and you do not define a dns provider, the state file gets corrupted and you can not remove these ghost dns resources.

workaround:

terraform state pull > terraform.tfstate
vi terraform.tfstate
# --> remove _dns_cname_record_  or _dns_a_record_  and increase serial
terraform state push terraform.tfstate

[Tom-Mann]

have you set the update server ? similar to the below ..
provider "dns" {
update {
server = "192.168.1.1"
}
}

[bflad]

Hi folks 👋

Given the original issue with update server is not set errors, the expected solution is to configure an update server either via the DNS_UPDATE_SERVER environment variable or a provider configuration block such as:

provider "dns" {
  update {
    server = "X.X.X.X"
  }
}

If you would rather remove the resource from Terraform state in this situation without applying the change, you can use the terraform state rm command.

If you have further questions about Terraform usage, please post a new topic in HashiCorp Discuss where there are more practitioners asking and answering questions, rather than this GitHub issue tracker which is mainly watched for bug reports and feature requests by the team maintaining the hashicorp/dns provider.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.