How to determine the culprit of the server not found error - hosting or domain registrar?

Question

Domain Name System

Good evening, once again, over the past month and a half, the site and subdomains have not responded.
The browser displays "Server not found", when trying to connect via ftp via Total Commander, the error is: Ip address not found.

How can I identify the culprit of the problem: hosting or domain registrar?

Answer 1

I believe that for this you need to have at least a superficial understanding of the principle, the basis of the DNS.

Answer 2

It seems to me that the domain registrar has absolutely nothing to do with it :D
Your problem may depend on many reasons, but most likely something is wrong with the servers in your NS (or A) records. To verify that the host is the culprit, simply go to the address in your NS (or A) records. Most likely, during the normal operation of the hosting, you should at least see something. If something is displayed, but the site does not respond, then you need to knock on those. registrar support, or check your DNS records yourself.

Answer 3

everything depends on where you have the NS server on the hosting or at the registrar.

Answer 4

If you own a console, then the commands that can help are whois (or jwhois) and dig. With the first command, look at which ns-servers the domain is delegated and its status (delegated / not delegated). With the second command, see what the ns-server gives when querying the domain, if everything is fine, see what the root NS servers of the domain zone give for your domain.

Answer 5

Ping the A entry and see if it works.
If the domain does not work for you, then by registering it in the host file, you must physically launch the site on your machine
. If this does not happen, then the problem is on the web server side
. If the site gives something like its worck, then this is an Apache error.