I moved my website to a new host and thought everything was fine, but it turned out not to be the case.
When accessing the site from my IP address, I can only see the old version of the site that's still on the old server. However, if I use an anonymizer or any other IP address, I'm able to see the updated version of the site on the new hosting. I'm not sure what the problem is - whether it's an issue with the old hosting, a delay in DNS updates from my ISP, or something else entirely.
If anyone has experienced this before or knows the solution, please explain. It's been more than 24-48 hours since I moved the site to the new host.
I've encountered the same issue multiple times when transferring my site, where even though a day has passed and my internal statistics show visitors on the new server, I'm still seeing the old site.
The problem can usually be solved by updating the DNS or refreshing the browser cache by pressing F5. For example, I experienced this issue with Firefox - I left the browser and when I opened it again, I was able to see the new website.
You probably just saved your data in cache, try to clean it or update your software (start from updating dns as said upwards or maybe update all of your programmes)
To update the DNS server records for a PBX, follow these steps in the management console:
1. Go to Parameters >> Network and change the PBX to "Dynamic (changing) public IP address". Restart the PBX services.
2. Repeat step 1, but specify a "Static (immutable) public IP address" instead. After clicking OK, restart the PBX services.
The PBX will then send a request to the Google DNS servers (assuming 8.8.8.8 is set as your main DNS server), and the server data will update the DNS records. However, it may take up to an hour for the changes to take effect, especially if the PBX services are restarted for around 30 minutes.
One potential issue is that even after changing the records on the public DNS server, remote users such as 3CX clients or desktop phones may still have the old IP address cached from their local DNS. They will have to wait until the TTL expires to make a new request and correctly resolve the new IP address of the PBX.
When you update the DNS settings for your domain to point to a new hosting provider, these changes need to propagate across the global network of DNS servers. This propagation process is influenced by various factors, such as the TTL (Time to Live) settings of your DNS records, caching mechanisms employed by ISPs, and the update policies of domain registrars.
In your specific scenario, the fact that you can only see the old version of the site when accessing it from your IP address indicates that your ISP's DNS has not fully updated to reflect the recent changes. When you use an anonymizer or a different IP address, you are essentially bypassing your ISP's DNS and accessing the updated version hosted on the new server. This behavior is a clear indication of partial DNS propagation.
To address this, there are several steps you can take. First, consider clearing your local DNS cache to ensure that your computer is not holding onto outdated DNS records. Then, you can switch to a different DNS resolver, such as Google Public DNS or Cloudflare DNS, to see if it provides updated results. This step will help you determine if the issue is isolated to your ISP's DNS.
Furthermore, it's essential to verify and double-check the DNS settings at your domain registrar. Ensuring that the name servers are correctly updated to reflect the new hosting provider's information is critical. If there are any discrepancies or errors in these settings, it can lead to inconsistent access to the updated version of your site.
In cases where DNS propagation delays persist beyond the typical 24-48 hour window, reaching out to your ISP to inquire about any specific caching or propagation issues on their end can provide valuable insights. Additionally, contacting your new hosting provider to confirm that the DNS settings and site migration have been completed correctly can help troubleshoot any potential technical issues.
While waiting for DNS propagation to complete, it's important to maintain patience and monitor the situation. In most cases, DNS updates can take up to 48 hours or more to fully propagate across the internet. By taking the aforementioned steps and staying proactive in your approach, you can navigate through this period of transition and ensure a smooth transition to your new hosting environment.