Latency based ALIAS creation

[thehouk]

Issue type:

• Bug report

cli53 version (cli53 --version):
cli53 version 0.8.15

OS / Platform:
MacOS/Ubuntu

Steps to reproduce:

cli53 import --file testdns.txt

file contains:
; Find and Replace the Origin domain in the entire document:
ORIGIN MEWO.

; Production Desktop Latency:
MEWO. 86400 AWS ALIAS A aws-nlb ZD4D7Y8KGAS4G true ; AWS routing="LATENCY" region="eu-west-2" healthCheckId="healthcheckid" identifier="UK"
MEWO. 86400 AWS ALIAS A aws-nlb Z26RNL4JYFTOTI true ; AWS routing="LATENCY" region="us-east-1" healthCheckId="healthcheckid" identifier="US"
MEWO. 86400 AWS ALIAS A aws-nlb Z24FKFUX50B4VW true ; AWS routing="LATENCY" region="us-west-1" healthCheckId="healthcheckid" identifier="USW"
MEWO. 86400 AWS ALIAS A aws-nlb ZCT6FZBF4DROD true ; AWS routing="LATENCY" region="ap-southeast-2" healthCheckId="healthcheckid" identifier="AU"
MEWO. 86400 AWS ALIAS A aws-nlb ZTK26PT1VY4CU true ; AWS routing="LATENCY" region="sa-east-1" healthCheckId="healthcheckid" identifier="SP"
.
.
.
rest of the dns.

output: the import completed successfully

-->

Expected behaviour

should see all 5 latency based ALIAS in Route53

Actual behaviour

the problem is that in route53 i can see only the last record (in this case SP), it rewrite the latency based alias.
records imported 24 out 30.
all other records are created successfully.