From owner-freebsd-net Mon Jul 24 8: 6:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id A5A7E37BAFC for ; Mon, 24 Jul 2000 08:05:43 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id JAA14013; Mon, 24 Jul 2000 09:05:39 -0600 (MDT) Date: Mon, 24 Jul 2000 09:05:39 -0600 (MDT) From: Nick Rogness To: "Roberto Nunnari, AGIE" Cc: net@freebsd.org Subject: Re: gateway strange behaviour for telnet and ftp In-Reply-To: <397C6440.37253C6C@agie.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 24 Jul 2000, Roberto Nunnari, AGIE wrote: > > But why it behaves that way only for telnet/ftp/nfs? When you telnet to a host on your network, the telnetd daemon running on that machine, issues a (PTR) request to your name server asking for name of the host connecting. A good test would be using nslookup: # nslookup Default Server: ns1.domain.com Address: 192.168.1.1 > 192.168.1.2 Server: ns1.domain.com Address: 192.168.1.1 *** ns1.domain.com can't find 192.168.1.2: Non-existent host/domain If that request makes your nameserver dial, you know you have found your problem. Solution: Either add entries in all of your /etc/hosts (or equivilent hosts file) or add a in-addr-arpa zone in your nameserver: zone "1.168.192.IN-ADDR.ARPA" { blah blah allow-query { 192.168.1/24; }; }; Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message