generally, the problem is that:
There was a site on the old virtual hosting. I wanted to transfer it to a vps. Ordered, installed Centos. Screwed the Centos web panel/
The registrar changed the DNS to those that came with access to the vps. Also, by default, the same DNS are exposed in the panel.
After the shift, the registrar's site is unavailable. I can't understand what's the matter, I waited for a while, still zero effect.
I understand that somewhere there is a jamb with an entry in the DNS, but where is still the same.
Tell me who can dig where.
I suspect that you were given dns to the vps - those through which the vps itself should resolve everything. like 126.96.36.199 or 188.8.131.52
and not at all those on which you need to hang your domains.
well, turn on the logic for a moment: how will those dns find out which domain names you added to your vps?
do you have any opportunity to edit dns records on these dns that you were given? I suspect not... actually, what surprises then? how should it all work according to you?
you need to either raise a dns server on your own vps, or use some third-party service, the same cloudflare.
In the Personal Account of the new hosting provider, you need to find a place where DNS is registered and register the same records as the previous hosting provider, with the exception of A type A record — here you will need to specify the IP address of the new server.
Checking the MX records of the domain
When transferring resource records, there is a danger of incorrect configuration of MX records, which inform various mail programs about where the desired mail server is located. If you do not transfer MX records from the previous server or fill them out incorrectly, the site owner may be left without mail on the domain for a long time - he will be able to send emails, but he will not receive incoming messages. At the same time, the sender of the letter to the mailbox on the domain will receive the following notification after sending:
If the MX records are not configured correctly within three days, the unreceived emails will be lost forever, and the sender will receive a notification that the email has not been delivered.
If the problem is fixed within the specified period, then incoming emails will not be lost, but will come later when DNS servers on the Internet exchange data about new DNS records. Updating DNS records takes from 2 to 72 hours.
Configuring NS Records
After configuring the resource records, you must specify the NS records of the new hosting provider in the domain registrar's personal account - redirect the domain to the new hosting. You can find out what NS records for a new hosting should look like in the reference materials provided by the hosting provider when buying a tariff, or by contacting the hosting technical support service. You should be especially careful — if the NS records of the domain are filled in incorrectly, the site will not work when updating DNS servers.
Above, we considered the situation when DNS records are edited on the hosting provider's side, and nothing else is hosted on the former server except for the transferred site. There are other situations:
The site owner stores several sites on the previous hosting.
In this case, it is not necessary to transfer DNS records and redirect the domain NS servers in the domain control panel to another hosting - they can be stored in the same place. It is only necessary to change the records of type A by specifying the IP address of the new server.
NS records and DNS records are stored in one place - in the domain control panel.
This happened to our client — the domain of his site was purchased through the provider Majordomo, which, in addition to hosting, also provides a domain registration service. This provider has NS records and DNS stored and edited in one place.
In this case, you also do not need to edit NS records and move DNS to another location, it is enough to specify a new IP address in a record of type A.