[73292] in North American Network Operators' Group
Re: filtering 1918 (was Re: Summary with...: Domain Name System ...)
daemon@ATHENA.MIT.EDU (Richard A Steenbergen)
Wed Aug 18 17:32:42 2004
Date: Wed, 18 Aug 2004 17:31:47 -0400
From: Richard A Steenbergen <ras@e-gerbil.net>
To: "David A. Ulevitch" <davidu@everydns.net>
Cc: nanog@merit.edu
In-Reply-To: <59922.24.5.40.13.1092863912.davidu@everydns.net>
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, Aug 18, 2004 at 02:18:32PM -0700, David A. Ulevitch wrote:
>
>
> <quote who="Richard A Steenbergen">
>
> > Is it really enough traffic that you, as a root server operator, can't
> > just suck it up and deal? Sure there are going to be a few folks who are
> > misconfigured, but I can't imagine that it is enough to cause operational
> > issues.
>
> No, no operational issues at all from RFC1918 space....
>
> http://www.as112.net/ (just to drop the most well documented example...)
That looks like a 1918 issue to me... Lets be clear about the difference
between a DNS query for 1918 space and a DNS query sources from 1918 space
which can never be returned too.
Yes I'm sure it is annoying, but the questions are:
How much EXTRA load does it really place on the rootservers?
Is it really so much load that you can't just chalk it up to a normal
part of the service being provided?
Or to put it another way:
How much computing power would I need to buy you so that I never have to
hear complaints about queries from 1918 space on a mailing list again? :)
--
Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
