Yes, the issue has been solved.
The problem was that my domain's nameservers were switched from DigitalOcean to Domain.com nameservers without my knowledge. A quick ICANN lookup shows this. This is why there was an issue with certbot.
Thank you all!
2 Likes