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: seasrv02.prop.co.hernando.fl.us
I ran this command: Requested Certification via Certify.
It produced this output: Validation of the required challenges did not complete successfully. dns :: DNS problem: NXDOMAIN looking up A for seasrv02.prop.co.hernando.fl.us
My web server is (include version): IIS
The operating system my web server runs on is (include version): Win Server 2012 R2
My hosting provider, if applicable, is: Government Domain
I can login to a root shell on my machine (yes or no, or I don’t know): I don’t know.
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you’re using Certbot): Certify the Web 4.1.6.0
Hello,
I have been trying to configure https access for my Moodle site on our office’s domain. We have configured net translation of the VM server that hosts the webpage but I continue to get NXDOMAIN errors when trying to access the site externally. Site works internally via http. We recreated this server on a VM from a physical one and I copied all the setting over exactly as they were, but it is not working stating in Certify that the DNS A record is not there and in browser a DNS_PUBLIC_FINISHED_NXDOMAIN error site cannot be found. Any help would be appreciated in regards to getting the site certified for https.
Thank you,
Chris