From owner-freebsd-hackers Fri Dec 15 1:54:48 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 01:54:47 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.98.60]) by hub.freebsd.org (Postfix) with ESMTP id 2C22D37B400 for ; Fri, 15 Dec 2000 01:54:46 -0800 (PST) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.11.1/8.9.3) with ESMTP id eBF9shx10461 for ; Fri, 15 Dec 2000 10:54:44 +0100 (CET) (envelope-from kheuer@gwdu60.gwdg.de) Date: Fri, 15 Dec 2000 10:54:43 +0100 (CET) From: Konrad Heuer To: freebsd-hackers@freebsd.org Subject: Why does lpd cause a lot of DNS traffic? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While solving some special remote printing problems I saw (4.2-STABLE) that lpd verifies printer access from a remote host by a lot of name resolution requests (my /etc/hosts.lpd has more than 300 entries). When verifying a host lpd scans hosts.lpd from the first line to the first matching line *not* by string comparison (hostname) but by requesting a name resolution for each entry (line by line) and comparing the INET address. For a heavily loaded printer server (as mine is) this seems not be a good idea ... but maybe there's a good reason to to this? Regards Konrad Heuer Personal Bookmarks: Gesellschaft f=FCr wissenschaftliche Datenverarbeitung mbH G=D6ttingen http://www.freebsd.org Am Fa=DFberg, D-37077 G=D6ttingen http://www.daemonnews.o= rg Deutschland (Germany) kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message