From owner-freebsd-hackers Mon Aug 25 10:21:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24868 for hackers-outgoing; Mon, 25 Aug 1997 10:21:30 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA24858 for ; Mon, 25 Aug 1997 10:21:21 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0x32oi-0001Eb-00; Mon, 25 Aug 1997 11:20:40 -0600 To: sthaug@nethelp.no Subject: Re: Broken resolver/named Cc: brian@awfulhak.org, mike@smith.net.au, freebsd-hackers@freebsd.org In-reply-to: Your message of "Sun, 24 Aug 1997 18:24:39 +0200." <28457.872439879@verdi.nethelp.no> References: <28457.872439879@verdi.nethelp.no> <199708241154.MAA00755@awfulhak.org> Date: Mon, 25 Aug 1997 11:20:40 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <28457.872439879@verdi.nethelp.no> sthaug@nethelp.no writes: : Read RFC 1535 to see why having this search behavior as default is not : a good idea (it's a security hole, and generates a lot of unecessary : traffic). Yes. At one time BIND used to do this. If you have no domain name set for your machine, then it uses the last n-1 parts of the hostname. If you have a machine named fred.com, then your domain name is .com, and a lookup of localhost will find localhost.com, which isn't quite what you wanted, and will likely cause you to generate bogons that get caught in our packet filter :-(. It is interesting to see the number of port scanners that people are running from hosts that are misconfigured in this manner :-). Warner