You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I know, the standard treats both values with and without the trailing dot as valid, where the former is preferred. Also, the route53 docs say the same. Still, it's pretty confusing when the input doesn't match the output.
Domain names that end in a dot are called absolute, and are taken as complete. Domain names which do not end in a dot are called relative; the actual domain name is the concatenation of the relative part with an origin specified in a $ORIGIN, $INCLUDE, or as an argument to the master file loading routine. A relative name is an error when no origin is available.
Amazon would appear to actually be the one at fault here, since they treat all domain names as absolute whether they end in a dot or not. cli53 has to export those records as absolute since that's what Amazon means. Other DNS services will interpret them as relative domain names, which means your "cname.vercel-dns.com" would be interpreted as "cname.vercel-dns.com.vercel-dns.com." (assuming it was in a zone for "vercel-dns.com."), which is not the same record that R53 is providing. But once it's been corrected, there's not any real way to know if the original was correctly or incorrectly specified.
Issue type
cli53 version (cli53 --version)
built it from source using
go get github.com/barnybug/cli53/cmd/cli53
as of Mon 19 Apr 2021 01:57:46 PM CEST. If I run this command it returnsOS / Platform
OS: NixOS 20.09 (Nightingale) x86_64
Host: 20EN0006MZ ThinkPad P50
Kernel: 5.4.100
Shell: zsh 5.8
Terminal: alacritty
CPU: Intel i7-6820HQ (8) @ 3.600GHz
GPU: NVIDIA Quadro M2000M
Memory: 15842MiB / 23953MiB
Steps to reproduce
Expected behaviour
A hosted zone with exactly same identical records to the old one
Actual behaviour
most of the records have a trailing dot. The way one notices is by doing this:
the output shows a lot of these:
Note the trailing dot in the record on the 2nd line, from
new.domainname.json
The text was updated successfully, but these errors were encountered: