From owner-freebsd-security Sat Jan 29 8:47:25 2000 Delivered-To: freebsd-security@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 359CF15281 for ; Sat, 29 Jan 2000 08:47:21 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id RAA13431; Sat, 29 Jan 2000 17:46:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Michael Bryan" Cc: freebsd-security@FreeBSD.ORG Subject: Re: Continual DNS requests from mysterious IP In-reply-to: Your message of "Sat, 29 Jan 2000 08:42:46 PST." <200001290842460680.22E3EFC9@quaggy.ursine.com> Date: Sat, 29 Jan 2000 17:46:54 +0100 Message-ID: <13429.949164414@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200001290842460680.22E3EFC9@quaggy.ursine.com>, "Michael Bryan" wri tes: > > >On 1/29/00 at 8:34 AM Samara McCord wrote: > >>But this also brings up my other >>point. Correct me if I'm wrong, but my DNS servers shouldn't ever have >>to deliver the MX records for aol.com (or any domain for which I don't >>serve), except to my own internal machines and for my own customers, right? > >If somebody has manually setup their system to use you as a DNS resolver, >then you will get packets for any and all DNS requests they make, no matter >where they are on the Internet. Not a very smart way to do things, mind >you, but I've seen it before, usually from customers of mine who moved a >computer from work or another ISP and kept their old DNS settings. I don't >think that's what's going on in your case, though... Tell named to only recurse for your own IP range (takes code hacking). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message