Why do you focus to “configure your settings for your specific OS to use Google’s Public DNS”? Google’s Public DNS has really much privacy concerns and is not the fast DNS resolver in all cases!
I’m running dnsping under real user environments (via WiFi which is mostly used nowadays) from home (and not via a cloudserver with a 10 Gbit interfaces directly connected to DE-CIX/Google/etc.) and I was astonished and want to share with this community:
Hey @thomasmerz,
In this guide, our focus was to give a solution to someone getting this alert, but because the scenarios might be many, we decided that changing (or reverting) to Google’s DNS could be a good “first step” to clear this alert.
Thank you a lot for your input, we will make a summary post under the alert’s guide!
Hi @Ancairon , I agree that your “first step” is just an “example” - it would really be nice if you can update/add some more information about some other public DNS resolvers as well
The dnsping is more the “nerdy” stuff and really hard to do for the most non-technicians (aka “normal user”). But it gives someone a real life example. I hope my contribution can help you and others to get a different view on performance of DNS resolvers
@thomasmerz thank you for your input, we will add a summary with your report in the dns_query_time_query_time alert guide so we don’t lose this information and then we will amend the current troubleshooting suggestions.
,
