Authoritative Resources for Public DNS Pinging

Wed Feb 9 01:15:32 UTC 2022

Orly? 64 bytes from 8.8.8.8: icmp_seq=10937 ttl=112 time=44.408 ms
64 bytes from 8.8.8.8: icmp_seq=10938 ttl=112 time=43.480 ms
64 bytes from 8.8.8.8: icmp_seq=10939 ttl=112 time=57.839 ms
64 bytes from 8.8.8.8: icmp_seq=10940 ttl=112 time=38.816 ms

-LB

Ms. Lady Benjamin PD Cannon of Glencoe, ASCE
6x7 Networks & 6x7 Telecom, LLC 
CEO 
ben at 6by7.net <mailto:ben at 6by7.net>
"The only fully end-to-end encrypted global telecommunications company in the world.”
ANNOUNCING: 6x7 GLOBAL MARITIME <https://alexmhoulton.wixsite.com/6x7networks>

FCC License KJ6FJJ

> On Feb 8, 2022, at 12:39 PM, Lukas Tribus <lukas at ltri.eu <mailto:lukas at ltri.eu>> wrote:
> 
> Hello,
> 
> On Tue, 8 Feb 2022 at 18:56, Mike Hammett <nanog at ics-il.net <mailto:nanog at ics-il.net>> wrote:
>> 
>> 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?
> 
> This was just posted by Matthew Walster on the outages list (since
> 8.8.8.8 stopped responding to ICMP somewhere):
> 
> https://peering.google.com/#/learn-more/faq <https://peering.google.com/#/learn-more/faq>
> 
> 
> Lukas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220208/31db8480/attachment.html>