`dyn_record` fails with records for the top level domain

[hashibot]

This issue was originally opened by @jbarreneche as hashicorp/terraform#11078. It was migrated here as part of the provider split. The original body of the issue is below.

---

Terraform Version

$ terraform -v
Terraform v0.8.2

Affected Resource(s)

• dyn_record

Terraform Configuration Files

resource "dyn_record" "root_restorando_net" {
  zone = "restorando.net"
  name = ""
  ttl  = 90

  type  = "A"
  value = "127.0.0.1"
}

Debug Output

https://gist.github.com/jbarreneche/78f6752aff380186fd0897c28a7d96f1

Expected Behavior

An "A" record created at the top level domain

Actual Behavior

Fail with 400 bad request. Probably the request in this case is malformed.

Steps to Reproduce

1. terraform apply (with the dyn credentials and the above terraform file)

Important Factoids

This also happens when trying to modify an existing record at that given level (this record were imported manually, and we wanted to change the TTL).

[ipmb]

Haven't dug deep into this, but I'm guessing it is a result of https://github.com/nesv/go-dynect/issues/21

[nesv]

I have a potential fix in nesv/go-dynect#22, but I have no means of testing this against live data; I do not have any Dyn credentials.

Would someone with Dyn credentials be able to test the changes, and see if they work as intended?

[nesv]

Thanks to @ipmb for testing the changes in nesv/go-dynect#22, a fix has been merged in, and tagged as v0.5.3.

[rata]

@nesv I use this provider too, let me know if I can help the next time :-)

[nesv]

Fantastic! Thank you very much, @rata!