Dynamic DNS (route53) failing after moving from virtual machine to sg-3100
Craquehead last edited by Craquehead
This post is deleted!
Craquehead last edited by
As is always the case, I was able to resolve this immediately after posting.
the comments in https://www.ceos3c.com/cloud/aws-with-pfsense-part-2-route53-dyndns-with-pfsense/ suggest that there is some uncertainty around prefixing the zone id with "us-east-1" which may have changed around 2.4.0. My old VM had been through many upgrades so perhaps it was still working with the old value while my fresh install on the sg-3100 was not.
I deleted the dynamic DNS entry entirely and recreated it from scratch with just the hosted zone ID sans the us-east-1 prefix, and it worked immediately.
Hopefully this proves useful to someone in the future.