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.
My domain is:mpgps.co
I ran this command: wac.exe in powershell
It produced this output: Preliminary validation for 97.74.103.4 failed: no TXT records found
My web server is (include version):IIS version 10.0.18362.1(Windows 10 Pro)
The operating system my web server runs on is (include version):Windows 10 pro
My hosting provider, if applicable, is: local dns server using bind
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):
@JuergenAuer 1.how i can get ssl certificate for my local web server. Is there any option?
2. how i can get ssl certificate for my web server iis where dns get resolves by AWS Route 53 ?I tried but it ask me to add txt value for domain name:_acme_challenge.hrmsho.mpgpsdc.com.
3. Do i need to take my local bind dns server to public address where it can resolves any internal domain name.?
What i can do in such senarios. Kindly help me .Thank you.
@JuergenAuer my dns server resolves domain name in LAN. But how i can generate ssl for local server bby using local dns server which works fine in LAN. Kindly help sir.
You can not use your local DNS server to generate a certificate unless it is also the DNS server that is authoritative and internet facing for your domain. But that does not appear to be the case.
Public NS records for mpgps.co point to ns08.domaincontrol.com and ns07.domaincontrol.com which I believe are GoDaddy DNS servers. So you would need to use a client that can work with the GoDaddy DNS API or manually create your TXT records there.
You can certainly use Route53 as your public DNS provider. But you have to update your nameserver settings at GoDaddy to point to the AWS ones. You would first create the zone in Route53 in order to know which nameservers to set. Then, take those over to GoDaddy and change from the default nameservers to the Route53 ones you were assigned.