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.
It produced this output:
domain: rtitek.com
type: None
detail: DNS Problem: query timed out looking up A for rtitek.com (the same message for www.rtitek.com.)
My web server is (include version): apache 2.4.18
The operating system my web server runs on is (include version): ubuntu 16.04.4
My hosting provider, if applicable, is: running on dedicated server
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): no
ns2.hostulator.com doesn’t exist. It looks like you made a typographical error when entering your nameservers at your domain registrar. You probably meant dns2.hostulator.com.
I just looked at my bind9 zone file for rtitek.com, and the ns records are set properly to dns1/dns2 acordinly. what dns server are you using? I am wondering if the server you nslookup’ed against wasn’t propagated yet. Do you still get the same results today? Thank you so much for your help.
hostulator.com. 172800 IN NS ns2.hostulator.com.
hostulator.com. 172800 IN NS dns1.hostulator.com.
rtitek.com. 172800 IN NS ns2.hostulator.com.
rtitek.com. 172800 IN NS dns1.hostulator.com.
Unless you changed it within the last few minutes, those are the current nameservers.
HI again… OK. I’ve figured out my domain issues with my domain controler namecheap.com… whois.domaintools.com now shows rtitek.com with dns1/dns2 .hostulator.com as its dns servers. I am getting a new error from certbot:
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
(admin@gandolf:pts/0)-<~> #