I just don't know how to figure out how to get Let's Crypt to validate My IIS Website can someone help please?
Here is the Error Am getting.
Plugin IIS generated source [Example Domain Name.com] with 1 identifiers
Plugin Single created 1 order
Cached order has status invalid, discarding
[Example Domain Name.com] Authorizing...
[Example Domain Name.com] Authorizing using http-01 validation (SelfHosting)
[Example Domain Name.com] Authorization result: invalid
[Example Domain Name.com] {"type":"urn:ietf:params:acme:error:dns","detail":"no valid A records found for [Example Domain Name.com]; no valid AAAA records found for [Example Domain Name.com]","status":400,"instance":null}
[Example Domain Name.com] Deactivating pending authorization...I though it's only at My Domain Registrar I suppose to edit my DNS Host Record not the IIS Site?
Hello @Cobra, welcome to the Let's Encrypt community. 
When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:
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. crt.sh | 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:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
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):
Thank you for assisting us in helping YOU!
You need to have an A record (for IPv4) in your DNS so people can find your server's public IP address using your domain name. (and/or AAAA record for IPv6)
This affects everyone including Let's Encrypt when you ask it to use an HTTP Challenge to validate your domain. This is what you did. Programs need the IP address to connect with.
This site is helpful to test new setups: https://letsdebug.net
As @MikeMcQ says, your domain needs to point to your server IP addresses so that the name resolves to that particular server.
The best way to get started is usually to get a basic http website working on your server (accessible from the public internet, not just within your corporate network), then add you certificates.