Do Azure DNS and Route 53 export the same format?
No. Azure DNS offers a zone-file export, while the documented Amazon Route 53 CLI workflow lists record sets as JSON. Recon.ph accepts a documented subset of BIND-style zone files and flat hostname,type,value CSV or JSON records; do not upload the nested Route 53 JSON directly and assume it has been fully interpreted.
Azure DNS: portal export
In the Azure portal, open DNS zones, select the public DNS zone, and select Export. Azure downloads a text zone file. Preserve the original for future comparison. The Azure export can contain multiline SOA data and other provider-specific constructs that the current Recon.ph parser does not fully support; check import notes and compare only the supported records.
With the Azure CLI, on an authenticated account with the required access:
az network dns zone export \
--resource-group YOUR_RESOURCE_GROUP \
--name example.com \
--file-name example-com.zone
Exported records are configured DNS evidence, not a test of current reachability. Check you selected the correct subscription, group and zone. Do not paste account secrets into a zone file.
Amazon Route 53: record-set inventory
Route 53's CLI can list records in a hosted zone:
aws route53 list-resource-record-sets \
--hosted-zone-id YOUR_HOSTED_ZONE_ID \
--output json > route53-records.json
This command requires configured AWS CLI credentials with appropriate authorization. The output is a nested ResourceRecordSets structure; Recon.ph does not treat that file as a flat host-record list. For conventional ResourceRecords entries, a separate local conversion with jq produces compatible CSV:
jq -r '["hostname","type","value"],
(.ResourceRecordSets[]
| select(.ResourceRecords != null)
| . as $set
| .ResourceRecords[]
| [$set.Name, $set.Type, .Value]) | @csv' \
route53-records.json > inventory.csv
That converter intentionally omits Route 53 AliasTarget record sets and provider metadata; it is not a complete Route 53 backup or a reverse-import mechanism. Preserve and review the original JSON for alias targets, policies and routing-specific values. A missing converted row must not be interpreted as a removed asset. Confirm the CSV header and inspect a few rows before importing it into the workspace.
Choosing evidence for comparison
Use equivalent provider, account and zone coverage for the baseline and current inventories. Mixing an Azure zone file with selected public lookups, or comparing a Route 53 CSV that omits aliases with an earlier complete inventory, can manufacture false differences. See our worked snapshot example and review checklist.