I have set my Elastic IP as the A record.
Thanks for the swift response. When I checked my instance config in AWS, I see that it does have a public ipv4 address.
Is there anything else I need to do to make it public and available?
The nameserver used is from https://check-your-website.server-daten.de/?q=nithyasanghachat.org - so it’s your name server.
I don’t know if these amazon nameservers are slow.
Ok, I installed certbot and attempted to perform DNS challenge instead of the HTTP challenge. I had also setup an AWS user who has access to change record sets in Route-53. Then I setup those credentials in ubuntu VM to be used by certbot.
Is there anything else that I need to do in AWS Route-53 config for the DNS challenge to succeed?
What’s the Certbot command you used, and what’s the full output of the command?
That’s an odd outcome (if it was configured correctly).
There are two Route 53 hosted zones for nithyasanghachat.org..
But one is in fact hosted on ns-1766.awsdns-28.co.uk. and 3 other com, net and org nameservers.
Certbot might be finding and modifying the hosted zone that isn’t in active use.
Wow, I dont know why Route-53 registrar created one more HostedZone, while I was creating one.
In any case, I deleted the HostedZone in whose config I kept adding recordsets.
Now when I ran the same command, my certificate got created. Yay!!!
Thanks for that valuable pointer.