On a high demand & high throughput website, in order to have high availability, I have three servers that serve queries at mydomain.com. I set three A-records on GoDaddy in order to have a round-robin load balancing on my servers (each having a unique IP, and not hosted on GoDaddy):
A mydomain.com IN 188.8.131.52 A mydomain.com IN 184.108.40.206 A mydomain.com IN 220.127.116.11
Thus, each server should receive 33.3% of the incoming queries.
I was under the impression that, if an HTTP request on 18.104.22.168 fails, then the browser and other apps would retry and eventually reach 22.214.171.124 and 126.96.36.199.
I found out that if server 188.8.131.52 goes down, then some users who previously accessed the website through 184.108.40.206 are never able to reach mydomain.com, even if there are two other servers available. Could it be due to DNS caching on their side? If so... how to solve that? They are never able to reach my site.
- The problem has not been reported on browsers but on Linux computers that use NodeJS applications (which use
- Is GoDaddy DNS management appropriate for what I want to do?
- Is there a better strategy to use to prevent domain downtime?
- Is there a better DNS management platform than GoDaddy?
I have read about other DNS systems which detect when a server goes down and which simply remove that server from its list of A records; this would be an option to solve my issue! But are there options with my current setup on GoDaddy?
Tell me how you manage your domain name high availability.