driftctl now relies on the FQDN to read a resource with the terraform provider and compare two route53 records. This fixes some issues in edge cases where we couldn’t find two corresponding records if they were not located in the same zone (as the zone is sometimes included in the record’s name, which hindered their recognition).