Brooklyn Zelenka
Brooklyn Zelenka
@bmann still open after trying the CLI v2.9.x?
@bgins can you include an example subdomain that didn't get deleted?
Also do you happen to know if there was a failure HTTP response?
> Noticing some else strange here as well. The above is true when trying to reach the site in Firefox on both attempts, but opening the site in another browser...
This is what I get in FF:
Also I get this from nslookup: ``` ❯ nslookup huge-young-wide-leopard.fission.app Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: *** Can't find huge-young-wide-leopard.fission.app: No answer ``` Feels like a caching thing
I'll look at Route53 directly; one sec...
So, this is definitely a caching thing. The DNSLink record is still there (which we should fix), but the CNAME is gone. The CNAME has a TTL of 86400 seconds...
I'd like to get rid of that DNSLink. AWS changed the API a few months back to expect an array, and we changed at least some of our calls (must...
Updated the solution section