Yes, we utilize alternative DNS servers to ensure optimal performance and reliability.
Yes, we utilize alternative DNS servers to ensure optimal performance and reliability.
I've recently faced video streaming problems on some sites using Akamai CDNs. It seems my Cloudfare DNS was the culprit, directing me to servers in distant locations and slowing down playback. This is prompting me to reassess the DNS servers I use for my PC and gaming devices. On one side, I'd sacrifice privacy for faster speeds, while on the other, I'd enjoy improved performance from CDNs. If you're experiencing similar streaming or download issues over a network, checking your DNS settings might help. Are there other options available to resolve this? Do you switch to different DNS providers or rely on your ISP's configuration?
I’m currently relying on Cloudflare DNS and haven’t faced any problems with the location of assigned CDN servers. However, this could be a potential reason to stick with your local ISP DNS servers. In my environment, we manage thousands of separate internet connections—over 5000 in total, nearing 10,000. Our guidelines state that the DNS servers programmed should never belong to the same provider. We also prefer variety, avoiding using the same set for every installation. This approach helps us prevent widespread outages; previously, we relied solely on one company’s primary and secondary servers, which experienced an 18-hour DNS failure and made it impossible to adjust remote router settings. Another concern is that Google DNS might mistakenly flag us as part of a DDOS attack, temporarily blocking access. Our engineers have the flexibility to choose any DNS provider, ensuring that issues with one won’t impact all our sites. Right now, I select three IP addresses from this list: 8.8.8.8, 8.8.4.4, 1.1.1.1 and 9.9.9.9, which are the ISP DNS IPs for a specific internet connection.
This approach isn't ideal because using different DNS servers on the same connection can lead to inconsistent results. Cloud9 handles their own DNS filtering while Google doesn't. This might cause your site to function unpredictably or switch between various CDN locations. Even with Google and Cloudflare, outcomes can vary based on their internal processes. For large businesses, it's better to maintain an in-house DNS cache for full resolution. Some providers like Netgate suggest this method to ensure you receive a clean response that reflects your network's actual topology, optimizing CDN performance for your specific ISP.
Yes, this is a very valid point, however we don’t program in DNS to the end user devices (DHCP or static). The DNS servers I mentioned are put into the firewall and gateway, and downstream devices use those as their DNS server. So the issue of bouncing between sources is limited by the caching in our networking equipment, and all clients should have the same results at a certain time.
Netgate is strongly suggested. I did not use that setup because Cloudflare was unstable for some domains while Cloud9 performed well.