I think we need to deliniate the conversation for human-memorable, on-demand needs vs. always-on configured needs.


A system always checking to see if "Internet" is up is different than "I think something is wrong, let me check".

For the always-on systems, how extensive do you want to get? What is your action if it's up? What is your action if it's down?



-----
Mike Hammett
Intelligent Computing Solutions

Midwest Internet Exchange

The Brothers WISP


From: "Mike Hammett" <nanog@ics-il.net>
To: nanog@nanog.org
Sent: Tuesday, February 8, 2022 11:56:44 AM
Subject: Authoritative Resources for Public DNS Pinging

Yes, pinging public DNS servers is bad.

Googling didn't help me find anything.

Are there any authoritative resources from said organizations saying you shouldn't use their servers for your persistent ping destinations?