[58893] in North American Network Operators' Group

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

RE: NAT for an ISP

daemon@ATHENA.MIT.EDU (William S. Duncanson)
Wed Jun 4 17:14:12 2003

From: "William S. Duncanson" <caesar@starkreality.com>
To: <nanog@merit.edu>
Date: Wed, 4 Jun 2003 16:13:32 -0500
In-Reply-To: <206b01c32adb$bdb472f0$1302a8c0@default>
Errors-To: owner-nanog-outgoing@merit.edu


 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

One would think so, wouldn't they?  It seems, however, not to be the
case.

- -- 
William S. Duncanson                        caesar@starkreality.com
The driving force behind the NC is the belief that the companies who
brought us things like Unix, relational databases, and Windows can
make an appliance that is inexpensive and easy to use if they choose
to do that.
- -- Scott Adams
 

> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On 
> Behalf Of Rubens Kuhl Jr.
> Sent: Wednesday, June 04, 2003 15:56
> To: nanog@merit.edu
> Subject: Re: NAT for an ISP
> 
> 
> 
> 
> ISPs that provide RFC1918 space should also provide recursive 
> DNS services
> that would stop all RFC1918 in-addrs before hitting root-servers
> and guidance to their users so they do the same on their servers 
> if they don't
> forward requests to the ISP recursive resolver.

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBPt5g/PNxJ1tT9oUNEQKzaACfTCUOgIWex2hewQeYTzguNb+UTFEAoMHj
NKdWopZhiRtyYW+r2W9r8czN
=3Utp
-----END PGP SIGNATURE-----


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