From owner-freebsd-isp Fri Nov 22 06:40:11 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA21197 for isp-outgoing; Fri, 22 Nov 1996 06:40:11 -0800 (PST) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA21179 for ; Fri, 22 Nov 1996 06:40:05 -0800 (PST) Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.8.3/8.8.3) with SMTP id JAA21238; Fri, 22 Nov 1996 09:39:41 -0500 (EST) Date: Fri, 22 Nov 1996 09:36:56 -0500 () From: Bradley Dunn To: Verdell Hicks cc: freebsd-isp@freebsd.org Subject: Re: Name Server Q In-Reply-To: <32952C9A.5AC@novalink.com> Message-ID: X-X-Sender: bradley@harborcom.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ummm...correct me if I am wrong, but I think INN looks up the names in hosts.nntp at startup. After that it just compares the IP of incoming connection requests to the IPs it has stored from the lookup of the names in hosts.nntp. IOW, no reverse lookup is done. -BD PS-If I am right does that mean I can be an MCI news admin...oooohhhh woooooowwwww! :-) > The problem appears to be in the PTR record in your DNS. Please > observe. > > nslookup news.novalink.com > Server: ns.pcy.mci.net > Address: 204.70.138.79 > > Non-authoritative answer: > Name: loki.novalink.com > Address: 192.233.90.158 > Aliases: news.novalink.com > > That much is perfect, BUT... > > nslookup 192.233.90.158 > Server: ns.pcy.mci.net > Address: 204.70.138.79 > > Name: loki.novalink.com > Address: 192.233.90.158 > > Since the PTR record does not resolve with the alias, newsfeed is > denying you > access. Please correct the PTR record so that is resolves identically > to > the A record. > > Thanks, > > Jeremy W. Powell > InternetMCI Usenet News Administrator