Domain does not connect to linode server

Hi there -

Thanks for reaching out with this. I started off by running a dig on your domain:

$ dig +short aleksaf.com

It did not return an IP address, which is what it should do if the DNS is configured properly. The first thing I would do is check that. You can use our DNS set-up checklist to help out.

The reason I bring up DNS is because when I try to navigate to your website, I get the following:

This site can’t be reached
aleksaf.com’s server IP address could not be found.

Try:

Checking the connection
Checking the proxy, firewall, and DNS configuration
ERR_NAME_NOT_RESOLVED

You did mention that this worked before, which leads me to believe that the DNS was configured correctly at one time. Did you change anything in your DNS configuration in the Cloud Manager?

You also mention the error that you received when running ifconfig. Since we can't see into your Linode's internals, it's hard to say what might be causing that although it could be related. To help as best I can, I want to refer you to our static networking guide which might be useful to you:

Static Networking

I'm also going to add some tags to this post to give it more visibility to other members of the Linode Community who might be able to offer more help than what I've given.

Hey there,

I just wanted to add, I took a look at this issue as well and I believe I found two specific DNS related issues happening here.

First, your domain has conflicting NS records:

 dig ns +short aleksaf.com
ns4.linode.com.
ns48.domaincontrol.com.
ns1.linode.com.
ns47.domaincontrol.com.
ns2.linode.com.
ns3.linode.com.

In general, you should have NS records for either Linode or GoDaddy, but this shows both (ns48.domaincontrol.com and ns47.domaincontrol.com are GoDaddy Nameservers). I would recommend removing those nameservers from the list at your registrar so only the Linode nameservers appear. This will prevent conflicts between the Linode nameservers and the GoDaddy nameservers.

The second issue I saw was that there was no A record for your domain on the Linode nameservers:

dig @ns1.linode.com a aleksaf.com

; <<>> DiG 9.10.6 <<>> @ns1.linode.com a aleksaf.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34096
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;aleksaf.com.            IN  A

;; AUTHORITY SECTION:
aleksaf.com.        86400   IN  SOA ns1.linode.com. aleksandra\.fiedorowicz.uconn.edu. 2021000010 14400 14400 1209600 86400

;; Query time: 101 msec
;; SERVER: 162.159.27.72#53(162.159.27.72)
;; WHEN: Fri Aug 14 17:07:39 EDT 2020
;; MSG SIZE  rcvd: 119

There is no IP answer section in that response, which indicates the A record is not there. When I run dig @ns1.linode.com a aleksaf.com +short the response is blank. You mentioned you had added an A record, so on a hunch I checked for a common misconfiguration:

dig @ns1.linode.com a aleksaf.com.aleksaf.com +short
xxx.xxx.xxx.xxx

For privacy's sake I have hidden the server's IP address. This issue occurs when you add the A record to DNS manager and enter the domain in the hostname field. If you wish to add an A record to the DNS manager for the base domain aleksaf.com, you should leave the hostname field blank. Enter your Linode's IP address in the IP address field, then submit it. After a few minutes the command dig a +short aleksaf.com should return your Linode's IP address.

I hope this helps!

Thank you so much! I fixed the name servers and A record and it is working now!