Website Stuck Between Servers
Hi everyone, I’m facing a strange issue with my website after attempting a server migration. I moved the site to a DigitalOcean server, but later decided to return to my previous hosting provider. I reverted the DNS and confirmed that the domain appears to point to the old server. However, the website still loads content from the DigitalOcean server. Interestingly, if I shut down the DigitalOcean droplet, the website stops responding completely. I’ve also noticed that accessing the domain with the WHM port works, but domain.com/whm does not. I’ve checked the DNS settings, but I’m still confused. Has anyone experienced this kind of DNS or server routing issue? Any suggestions would be appreciated.
-
I had a similar DNS issue during a server migration, and in my case, an old A record was still directing traffic to the previous server. I would double-check the authoritative nameservers, A and AAAA records, and DNS propagation from a few different locations. Since the site stops responding when the DigitalOcean droplet is shut down, it definitely sounds like some traffic is still reaching that server. Checking the DNS zone on both hosting accounts may help pinpoint the issue.
0 -
When you make DNS changes, there is a TTL (time to live value) on each record. Depending upon the TTL on the records you changed, it could be up to four hours before you see the site at the proper location. If you were changing authoritative nameservers, that could also result in an extended period where you keep seeing the website at its old location instead of at its preferred current location.
Of course, your local resolver on your Windows/linux PC and/or the DNS servers that your machine is querying could be holding stale DNS data. If you are positive you have all the proper/correct DNS records in place at the proper place, then you just need to wait it out.
m
0 -
This is a great site to check for DNS records:
0
Please sign in to leave a comment.
Comments
3 comments