On Sat, 2 Nov 2002, Kevin Weslowski wrote:

> Hi again,
> 
> well, maybe it is some sort of DNS error...well, SSH/http started
> working last night again, but not ftp...ftp started working this
> morning...
> 
> I did a capture of an unsuccessful ftp session last night and there were
> several packets sent to my ISP's DNS server, querying about 192.168.1.1
> 
> Why would it try to resolve an IP, and an internal network IP at that?
> This morning I also captured a successful ftp session and there are only
> 2 packets re: DNS...1 from my machine and a reply from the DNS server...
> 
> I don't know what this means, but if someone can help, I'd appreciate
> it...
> 
    Each computer should know from its /etc/hosts file how to translate
between name and IP number 192.168.1.1.  For example, a line "192.168.1.1
mycomputer.junk.com mycomputer" says that "mycomputer.junk.com" and
"mycomputer" mean IP number "192.168.1.1".  The first choice to resolve IP
vs name is /etc/hosts if files is first in the "hosts:  ..." line of
/etc/nsswitch.conf.  For example, "hosts: files nisplus nis dns" puts
files first and dns last.  Is this the way you've set things up?  If not,
try it.

-- 
Steven Yellin



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to