Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
OK guys, I finally found the answer. Even though the error thrown was complaining about the A record, that wasn’t what was causing it (the A record was fine). The reason it was failing was because I didn’t set up CNAME records for the domain. Took forever to figure this out, thought I’d post the answer in case someone else runs into this problem.
There are no issues in our systems at this time but a massive DNS provider “Dyn” is experiencing a massive DDoS attack at this time. While our droplets are configured to use Google Public DNS instead, droplets trying to reach out to other sites that utilize Dyn DNS will experience connection issues.
https://www.hackread.com/ddos-attack-dns-sites-suffer-outage/
I didn’t think so but I was grasping at straws. Any other ideas why I might be having this problem? I’m not finding any difference in what worked before and what isn’t working now. EDIT: Oh wait - do you think the certificate authority letsencrypt uses might be affected then?