Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command:
sudo certbot -d $DOMAIN -d $WILDCARD --manual --preferred-challenges dns certonly
It produced this output:
_acme-challenge.maheshkhali.com
TXT Record
aqnSqDEMwCe8wdi5IWPyQUEfjl2fQDAaeXsPWUYczEA
TXT Record
_acme-challenge.maheshkhali.com
AHNMfMgiTSmm6dNFQmhF6ANnO6PrZ3vA1ukyUO91sbA
configured it to dns zone of lightsail but when checking in MX Lookup tool, it showing DNS record not found.
The operating system my web server runs on is (include version):linux
My hosting provider, if applicable, is: AWS ligtsail
I can login to a root shell on my machine (yes or no, or I don’t know):Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
When certbot authenticates via DNS, it requires either manual interaction or an API plugin.
You may need to look into using this parameter (and its’ requirements): --dns-route53
If you understand how the Internet uses DNS, then you can see how it might fail to resolve your TXT record(s).
Because: Your list of DNS servers does not match the Internet list of DNS servers (for your domain).
You need to correct that problem first.
It’s my default NS of Route53 but as per lightsail SSL configuration tutorial,Need to replace the NS route53 with lightsail NS.For that reason, i edited NS of route53.
