Error during terraform test and terraform apply

[Dnelre]

Terraform CLI and Provider Versions

Terraform v1.8.1
on linux_amd64

• provider registry.terraform.io/hashicorp/dns v3.4.1

Terraform Configuration

terraform {
  required_version = ">= 1.5"

  required_providers {
    dns = {
      source  = "hashicorp/dns"
      version = "3.4.1"
    }
  }
}

resource "dns_cname_record" "dns_record" {
  cname = "deploy-test.company.com."
  name  = "deploy-test"
  zone  = "company.com."
}

Expected Behavior

A CName record is created.

Actual Behavior

Error happenes with error message;

│ Error: Plugin did not respond
│
│ with dns_cname_record.dns_record,
│ on dns.tf line 19, in resource "dns_cname_record" "dns_record":
│ 19: resource "dns_cname_record" "dns_record" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may contain more details.

Steps to Reproduce

1. terraform init
2. terraform plan
3. terraform apply

How much impact is this issue causing?

Medium

Logs

https://gist.github.com/Dnelre/93c9d39dcd7f53825013dfe2e193b22a

Additional Information

DNS_UPDATE_PASSWORD, DNS_UPDATE_REALM, DNS_UPDATE_SERVER and DNS_UPDATE_USERNAME is set during runtime.

We encounter this error both in terraform test and apply.

Every time we do terraform apply I notice sockets are created under /tmp/plugin*

Code of Conduct

• I agree to follow this project's Code of Conduct

[Dnelre]

The error mentions; The plugin logs may contain more details. How can we access these logs to investigate further?

[Dnelre]

Solved the issue.

krb5.conf file did not like this format under [realms];

[realms]
domain.com = { kdc = dns-server.domain.com }
domain2.com = { kdc = dns-server.domain2.com}

had to change it to;

[realms]
    domain.com = {
        kdc = dns-server.domain.com
    }
    domain2.com = {
        kdc = dns-server.domain2.com
    }

[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.