DNS can't move the site

[PrimoPierotz]

Hello.
Essentially, the issue at hand is that there was a website on an old virtual hosting service that needed to be transferred to a VPS. Consequently, Centos was ordered and installed, and the Centos web panel was connected. Additionally, the registrar changed the DNS to match those provided with access to the VPS. After the switch, however, the registrar's site became unavailable. Despite waiting for some time, no progress was made in identifying the problem.

It is clear that there is an issue with the DNS entry, but the exact location of the problem remains unknown. Therefore, assistance is required to identify where the mistake is.

[brandsmith]

It appears that the DNS provided for the VPS might not be the correct ones to associate with the domains. It is important to note that the DNS given to the VPS are used to resolve everything within the VPS, such as 1.1.1.1 or 8.8.8.8, instead of being the ones on which domain names should be attached.

Considering this issue, it is crucial to think logically about how the DNS will identify the domain names added to the VPS. Since there may not be an opportunity to edit the DNS records given, a solution must be found.

One possibility is to launch a DNS server on the VPS or utilize a third-party service like Cloudflare to resolve the issue. Overall, it is essential to ensure the correct DNS are used to associate with the domains and avoid potential issues.

[john45]

To transfer resource records to a new hosting provider, one needs to ensure that DNS is registered in the Personal Account of the new hosting provider. In the process of transfer, it is important to configure MX and NS records correctly to prevent issues such as incorrect configuration of MX records. MX records help inform mail programs where the desired mail server is located, and if they are not transferred correctly, site owners may be left without mail on the domain for a long time.

Additionally, it is crucial to configure NS records correctly by redirecting the domain to the new hosting. This can be achieved by changing the records of type A by specifying the IP address of the new server. It's worth noting that if the NS records of the domain are filled in incorrectly, the site will not work when updating DNS servers.

In certain scenarios, such as when the client has multiple websites hosted on the previous hosting provider, it is not necessary to edit NS records and move DNS to another location. Instead, only records of type A need to be changed by specifying the IP address of the new server. Finally, it is possible that NS records and DNS can be stored and edited in one place, such as in the case of our client who purchased their domain through a provider with both hosting and domain registration services. In this case, there is no need to edit NS records or move DNS to another location, as specifying a new IP address in a record of type A will suffice.

[tevez]

Let's review the steps you've taken so far:
1. You had a website on an old virtual hosting service that needed to be transferred to a VPS (Virtual Private Server).
2. You ordered and installed CentOS and connected the CentOS web panel.
3. You changed the DNS settings at the registrar to match the ones provided with access to the VPS.
4. After the switch, the registrar's site became unavailable, and you've been waiting for some time without any progress.

Based on the information provided, it seems like the issue is related to the DNS propagation and configuration.

When you change the DNS settings, it can take some time for the new settings to propagate across the internet. This process is called DNS propagation, and it can take anywhere from a few minutes to a few hours, depending on various factors, such as the registrar, the number of DNS servers involved, and the caching policies of the internet service providers (ISPs).

To troubleshoot this issue, I would suggest the following steps:

1. Check the DNS settings: Ensure that the new DNS settings you provided to the registrar are correct and match the ones assigned to your VPS. Double-check the IP addresses, domain names, and any other relevant information.

2. Verify the DNS propagation: Use online tools, such as DNS lookup tools or websites like [DNSChecker.org](https://www.dnschecker.org/), to check the status of the DNS propagation. These tools can help you see if the new DNS settings have been updated across different DNS servers around the world.

3. Clear your browser cache: If the new DNS settings haven't fully propagated yet, your browser may still be using the old cached information, making the website appear unavailable. Try clearing your browser cache and refreshing the page.

4. Check your VPS configuration: Ensure that your CentOS web panel is configured correctly and that the website files are properly deployed on the VPS. Test the website by accessing it directly using the VPS IP address to see if the issue is specific to the DNS or if there's a problem with the server configuration.

5. Contact your registrar and hosting provider: If the DNS propagation is taking an unusually long time or you're still experiencing issues, reach out to your domain registrar and the hosting provider for the VPS. They may be able to provide more specific guidance or identify any potential problems on their end.

6. Consider a DNS propagation test: You can use a tool like [DNSPropagation.com](https://www.dnspropagation.com/) to test the DNS propagation and see if the new settings have been updated across different DNS servers. This can help you pinpoint the exact location of the issue.

By following these steps, you should be able to identify the root cause of the problem and find a resolution. If you have any further questions or need additional assistance, feel free to reach out, and I'll be happy to provide more guidance.

[Heelitelf]

First, ensure that the A records in your DNS settings point to the correct IP address of your VPS. Use tools like dig or nslookup to verify the DNS resolution from multiple locations. If the registrar's site is still down, check for any misconfigurations in the zone file or potential caching issues on your local DNS resolver. Remember, DNS changes can take time to propagate fully, but if it's been more than 48 hours, there might be a deeper issue at play.