nanog mailing list archives
Re: Authoritative Resources for Public DNS Pinging
From: Mike Hammett <nanog () ics-il net>
Date: Fri, 11 Feb 2022 09:11:56 -0600 (CST)
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 ----- Original Message ----- 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? ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP
Current thread:
- Re: Authoritative Resources for Public DNS Pinging, (continued)
- Re: Authoritative Resources for Public DNS Pinging Joe Greco (Feb 09)
- Re: Authoritative Resources for Public DNS Pinging Mark Delany (Feb 09)
- Re: Authoritative Resources for Public DNS Pinging Mike Hammett (Feb 10)
- Re: Authoritative Resources for Public DNS Pinging Mark Tinka (Feb 11)
- Re: Authoritative Resources for Public DNS Pinging Lukasz Bromirski (Feb 09)
- Message not available
- Re: Authoritative Resources for Public DNS Pinging J. Hellenthal via NANOG (Feb 09)
- Re: Authoritative Resources for Public DNS Pinging Brian Knight via NANOG (Feb 10)
- Re: Authoritative Resources for Public DNS Pinging Mark Tinka (Feb 11)
- Re: Authoritative Resources for Public DNS Pinging Mark Tinka (Feb 11)
- Re: Authoritative Resources for Public DNS Pinging Kord Martin (Feb 11)