SSH connection not working when using the DNS
I'm setting up a new linode. I'm able to SSH from my Windows laptop into the linode server with the ssh root@192.0.2.4 (using my actual IP address).
However, I get the following error messages when using my domain with SSH, but it's not due to needing the DNS propagation to take place since I set this up over five days ago and still get the following error:
C:\Users\username\OneDrive\Documents\example_domain>ssh -vvv root@example_domain.com
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
debug1: Reading configuration data C:\Users\username/.ssh/config
debug1: C:\Users\username/.ssh/config line 1: Applying options for *
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 'C:\Users\username/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 'C:\Users\username/.ssh/known_hosts2'
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug2: resolving "example_domain.com" port 22
ssh: Could not resolve hostname example_domain.com: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
3 Replies
✓ Best Answer
Clarification:
My domain name is set up with a DNS registrar external to my Linode servers.
I had to remove the DNSSEC record set up on the domain name server (DNS) since it prevented my domain name from propagating correctly to my Linode servers. The DNSSEC record must be set up on the Linode web servers, not the DNS.
CassandraD
Linode Staff
I looked through some of your previous posts and found your domain. When I run a dig, there are no nameservers listed for your domain.
You can see this by running this command:
dig NS $yourdomain.com +short
Since there were no results, I'd recommend making sure you've configured your nameservers with help from this guide.
First you'll want to make sure your nameservers are configured with your registar, which I've looked up and found is Squarespace. Have you gone to SquareSpace's domain dashboard and updated your nameservers there?. If not, you'll need to do that before DNS will work. You will need to point them to our nameservers listed here or whatever nameservers you intend to use. If you use our DNS manager, you'll need to use our nameservers.
You'll also want to update your DNS records to include the records as well. If you use our DNS manager, you can manage the NS records there.
While there could be something more complicated going on, it's really important to confirm that all needed DNS records are correct before any further troubleshooting can be done. I know you said that you've given things time to propagate, but from publicly available information, it doesn't seem like they are configured correctly yet so you may want to first read through our DNS overview to make sure that you're addressing everything that needs to be done.
I had to remove the DNSSEC record I had with the domain's DNS registrar because it prevented the domain name from propagating properly. Since the registrar is external to Akamai and Linode, I had to go to the registrar's site to remove the DNSSEC record.