[122567] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: History of 4.2.2.2. What's the story?

daemon@ATHENA.MIT.EDU (Frank Bulk)
Tue Feb 16 23:35:05 2010

From: "Frank Bulk" <frnkblk@iname.com>
To: "'Tomas L. Byrnes'" <tomb@byrneit.net>,
	"Joe Abley" <jabley@hopcount.ca>
In-Reply-To: <72F9A69DCF990443B2CEC064E605CE062778@Pascal.zaphodb.org>
Date: Tue, 16 Feb 2010 22:32:52 -0600
Cc: nanog@nanog.org
Reply-To: frnkblk@iname.com
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Our upstream ISP also has such a reciprocal secondary, too.

Frank

-----Original Message-----
From: Tomas L. Byrnes [mailto:tomb@byrneit.net] 
Sent: Tuesday, February 16, 2010 10:26 PM
To: frnkblk@iname.com; Joe Abley
Cc: nanog@nanog.org
Subject: RE: History of 4.2.2.2. What's the story? 

We actively sought reciprocal secondaries, and offered and received
reciprocal query hosts, from other regional ISPs when I was CTO @ ADN.

We saw it as "strengthening the regional Internet".

So our users used CTSnet as their tertiary NS, and CTSNet used ours, FE.

Of course, not CTS/CARI and ADN are all AIS, so the point is moot.

> -----Original Message-----
> From: Frank Bulk [mailto:frnkblk@iname.com]
> Sent: Tuesday, February 16, 2010 7:25 PM
> To: 'Joe Abley'
> Cc: nanog@nanog.org
> Subject: RE: History of 4.2.2.2. What's the story?
> 
> We do.  It's at our upstream provider, just in case we had an upstream
> connectivity issue or some internal meltdown that prevented those in
> the
> outside world to hit our (authoritative) DNS servers.  Of course,
> that's
> most helpful for DNS records that resolve to IPs *outside* our
network.
> 
> Frank
> 
> ===
> <snip>
> 
> For what it's worth, I have never heard of an ISP, big or small,
> deciding to place resolvers used by their customers in someone else's
> network. Perhaps I just need to get out more.
> 
> Joe
> 
> 



home help back first fref pref prev next nref lref last post