Date: Sat, 1 Jul 2000 19:47:15 +1200 From: "Mark Ibell" <marki@paradise.net.nz> To: <chad@DCFinc.com> Cc: <freebsd-stable@FreeBSD.ORG> Subject: Re: [Fwd: telnet/tcp problems in 4.0-RELEASE] Message-ID: <001101bfe330$b138faa0$0101a8c0@rf.org> References: <200007010532.WAA09706@freeway.dcfinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I understand what you were saying in your recent post (~23rd) but don't think that it completely explains my difficulties. The problem appears to be related to the absence of a domain extension. For example, on the machine in question (mars.econz.co.nz): # ftp localhost [pauses for 75 seconds] # ftp localhost.econz.co.nz [connects straight away] # ftp mars [pauses for 75 seconds] # ftp mars.econz.co.nz [connects straight away] # ftp shiva [pauses for 75 seconds] # ftp shiva.econz.co.nz [connects straight away] I think the reason incoming telnet fails is because of the fact that a 'login -h shiva -p' is spawned on localhost, where 'shiva' is of course without a domain extension. Here's my /etc/host.conf: # cat host.conf hosts resolv.conf # $FreeBSD: src/etc/host.conf,v 1.6 1999/08/27 23:23:41 peter Exp $ # First try the /etc/hosts file hosts # Now try the nameserver next. bind # If you have YP/NIS configured, uncomment the next line # nis Here's my /etc/hosts: 127.0.0.1 localhost 172.16.1.73 mars.econz.co.nz mars Here's my /etc/resolv.conf: domain econz.co.nz nameserver 172.16.0.1 Nothing flash here at all which is why I am now puzzled again. I mean, it used to work I swear! ----- Original Message ----- From: Chad R. Larson <chad@DCFinc.com> To: Mark Ibell <marki@paradise.net.nz> Cc: <freebsd-stable@FreeBSD.ORG> Sent: Saturday, July 01, 2000 5:32 PM Subject: Re: [Fwd: telnet/tcp problems in 4.0-RELEASE] > As I recall, Mark Ibell wrote: > > It does appear to be a dns problem after all. After renaming > > resolv.conf to resolv.conf.bak the problem is cured, although only > > hosts in the hosts file can be looked up. The strange thing is that > > both the 'nslookup' & 'host' commands both appeared to retrieve the > > correct information from the dns server (for both forward and reverse > > lookups) on our network. > > A week or two ago I posted about the circumstances in which host and > nslookup can give you misleading results, and a program to demonstrate > the fact. > > It has to do with how /etc/host.conf can be set to override what DNS > servers will tell you, but host, dig and nslookup query the resolver > directly, not using the gethostbyname(3) call, as an application > would. > > In your case, if "hosts" is in your /etc/host.conf ahead of "bind", > then you need to look for an entry in your /etc/hosts file that > would result in namespace overloading. > > And, check my earlier mail in the archives... > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.net > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001101bfe330$b138faa0$0101a8c0>