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: using ceritfy the web when it goes to tirgger response challenges
It produced this output: Validation of the required challenges did not complete successfully. Domain validation failed: www.eastgrandforks.us
DNS problem: SERVFAIL looking up CAA for www.eastgrandforks.us - the domain's nameservers may be malfunctioning BadRequest urn:ietf:params:acme:error:dns
My web server is (include version): IIS 8.0
The operating system my web server runs on is (include version): Windows Server 2012R2
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or 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):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
eastgrandforks.us to www.eastgrandforks.us: The server(s) for the parent zone (eastgrandforks.us) responded with a referral instead of answering authoritatively for the DS RR type. (64.140.185.18, 65.61.87.8, 65.61.87.9, UDP_-_EDNS0_4096_D_KN)
www.eastgrandforks.us/NS: The Authoritative Answer (AA) flag was not set in the response. (64.140.185.18, 65.61.87.8, 65.61.87.9, UDP_-_EDNS0_4096_D_KN)
You need to fix your DNS server for the www. name if you want Let's Encrypt to issue a certificate for it (as well as if you want users to be able to get to your site using it).
Since these are Domain Validation (DV) certificates the Domain Name System (DNS) is used extensively in the validation process as well a allowing us to assist here on Let's Encrypt community.
DNS Queries need to give consistent results from any location on the Internet, all your authoritative DNS Servers for the Domain need to also give consistent results as well.
Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher. Rate Limits are per week (rolling).
And to assist with debugging there is a great place to start is Let's Debug.