aws_route53_record strips trailing dots from FQDNs

[BBauman]

AWS presumes that all domains in Route53 are fully qualified, and thus a somewhere.com record is functionally equivalent to a somewhere.com. record. However, AWS will still retain the trailing dot if the user configures one, as demonstrated:

aws route53 list-resource-record-sets --hosted-zone-id (my-zone)
{
    "ResourceRecordSets": [
        {
            "Name": "(domain-with-trailing-dot)",
            "Type": "A",
            "TTL": 300,
            "ResourceRecords": [
                {
                    "Value": "(someIP)"
                }
            ]
        }
        ...
    ]
}

The Terraform AWS provider, however, will strip the trailing dot from any aws_route53_record name and fqdn field, both incoming (data) and outgoing (resources). For example:

resource "aws_route53_record" "dummy" {
  zone_id = (my-zone)
  name = "someurl.com."
  type = "A"
}

terraform plan

Terraform will perform the following actions:

  # module.admin-dns.aws_route53_record.dummy will be created
  + resource "aws_route53_record" "dummy" {
      + allow_overwrite = (known after apply)
      + fqdn            = (known after apply)
      + id              = (known after apply)
      + name            = "someurl.com"
      + type            = "A"
      + zone_id         = "(my-zone)"
    }

The fact that AWS treats all records as fully-qualified shouldn't matter to Terraform. Since AWS supports including or not including a trailing dot, Terraform should faithfully transmit the information as submitted. Similarly, Terraform should faithfully report the information as it exists in AWS, instead of removing the trailing dot as it does now.

Possibly related issues:
hashicorp/terraform#8511
#241
#1031

[justinretzolk]

Hey @BBauman 👋 Thank you for taking the time to file this issue. Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?

[BBauman]

Hey @BBauman 👋 Thank you for taking the time to file this issue. Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?

The above repro steps continue to demonstrate the behavior at least through provider release 3.46.0.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[Brian-Bauman]

Still relevant.