[32909] in North American Network Operators' Group
Re: Pinging routers for network status
daemon@ATHENA.MIT.EDU (Miguel A.L. Paraz)
Mon Dec 18 05:35:47 2000
Date: Mon, 18 Dec 2000 17:38:23 +0800
From: "Miguel A.L. Paraz" <map@internet.org.ph>
To: nanog@merit.edu
Message-ID: <20001218173823.C5679@mail.q-linux.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BEEPLMELPMPANJHCBHJEOEAMFGAA.mlevine@efront.com>; from mlevine@efront.com on Mon, Dec 18, 2000 at 01:12:17AM -0800
Errors-To: owner-nanog-outgoing@merit.edu
On Mon, Dec 18, 2000 at 01:12:17AM -0800, Matt Levine wrote:
> Well, although there's no entirely fool-proof way, We've found a better way
> of monitoring "real" outages/issues is to monitor the time required to setup
> a tcp connection to some "trusted" machines. For example, in our VA
> datacenter we monitor the time required to setup a connection with tier1
> providers (UU,BBN,DIGEX for example) nameservers (on port 53).. We've found
> it slightly more reliable than ICMP reqs, especially since when routers get
> busy, it shows as degradation vs. outage.
How does your "DNS ping" work, do you just open and close a TCP connection?
Or make actual requests? Like, "dig soa provider.net @ns.provider.net".
But perhaps if everyone starts doing this to the same box, it could be seen
as DoS?
--
http://www.internet.org.ph Internet and ISP's in the Philippines
http://www.ASARproject.org Artists for Social Action and Response
GSM Mobile: +63-917-810-9728
