From owner-freebsd-isp Tue Nov 18 10:01:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09877 for isp-outgoing; Tue, 18 Nov 1997 10:01:41 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from lithium.dowco.com (lithium.dowco.com [207.23.88.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09870 for ; Tue, 18 Nov 1997 10:01:35 -0800 (PST) (envelope-from kevinmck@dowco.com) Received: (from kevinmck@localhost) by lithium.dowco.com (8.8.7/8.8.7/CF.6) id KAA05601; Tue, 18 Nov 1997 10:01:19 -0800 (PST) Date: Tue, 18 Nov 1997 10:01:18 -0800 (PST) From: Kevin McKinnon To: John Brown cc: freebsd-isp@freebsd.org Subject: Re: DNS Reverse Lookup In-Reply-To: <01bcf443$a865a0b0$3e01017d@is01.vafibre.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 18 Nov 1997, John Brown wrote: > When My users attempt to download anything that requires reverse DNS > authentication (Like the 128 bit encryption stuff) they are being denied > because the ip cannot be associated with a name. > > Any Ideas on how I make this work, or a place that will has DNS related > examples. Hi John, You might check with your backbone provider to see if they've delgated reverse lookups for your IP block to your nameserver. It's possible that MCI still shows that *they* are doing the reverse lookups for your addresses. (This happened to me with SprintLink last year, same symptoms that you describe.) If they are still set to provide reverse lookups, you need to get *them* to delegate it to you... you can't have it changed yourself. Hope this helps... Best regards, Kev --------------------------------------------------------------------------- Kevin McKinnon, Network Engineer kev@dowco.com Dowco Computer Systems (dowco.com) http://www.dowco.com Member CLCU - The Committee for the Licensing of Computer Users