Date: Sat, 20 Nov 1999 16:05:58 -0800 From: "Majid Almassari" <majid@ibroadcast.net> To: <trouble@netquick.net> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@FreeBSD.ORG> Subject: Re: ftpd Message-ID: <010c01bf33b4$335e2140$0e91ddd1@balfourplace.com> References: <383635F6.6FB8EC5A@netquick.net> <002c01bf3325$3b9fd400$0e91ddd1@balfourplace.com> <3836BAF2.2BF62B9C@netquick.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Interesting,..well I don't see any delays in the ICMP packets, and since your DNS server is on the same switch on a T1, then that points to a Reverse DNS lookup . Did you restart named after you added the host in DNS server? I don't know the specifics but I would carefully look on how I would add such an entry. Due nslookup and see how long till you get results..Also create an entry for the host in /etc/host file in your local computer just to see if that makes a difference.. good luck. Majid Almassari, MSEE, MCP. Systems Administrator. iBroadcast, Inc. (206) 223-5540 http://www.ibroadcast.net ----- Original Message ----- From: TrouBle <trouble@netquick.net> To: Majid Almassari <majid@ibroadcast.net> Cc: freebsd-questions@freebsd.org <freebsd-questions@FreeBSD.ORG> Sent: Saturday, November 20, 1999 7:14 AM Subject: Re: ftpd > im on ISDN i hop from the box, and it is sitting on a T-1. the box > itself it sitti9ng in the same switch as the nameservers, ping times > from me > > 64 bytes from 199.72.47.2: icmp_seq=4 ttl=253 time=83.699 ms > 64 bytes from 199.72.47.2: icmp_seq=5 ttl=253 time=41.975 ms > 64 bytes from 199.72.47.2: icmp_seq=6 ttl=253 time=40.959 ms > 64 bytes from 199.72.47.2: icmp_seq=7 ttl=253 time=53.949 ms > 64 bytes from 199.72.47.2: icmp_seq=8 ttl=253 time=40.730 ms > 64 bytes from 199.72.47.2: icmp_seq=9 ttl=253 time=41.069 ms > 64 bytes from 199.72.47.2: icmp_seq=10 ttl=253 time=74.423 ms > > > now also ping times from the problem system to the nameserver > > > 4 bytes from 199.72.47.254: icmp_seq=8 ttl=254 time=1.426 ms > 64 bytes from 199.72.47.254: icmp_seq=9 ttl=254 time=5.490 ms > 64 bytes from 199.72.47.254: icmp_seq=10 ttl=254 time=5.011 ms > 64 bytes from 199.72.47.254: icmp_seq=11 ttl=254 time=3.037 ms > 64 bytes from 199.72.47.254: icmp_seq=12 ttl=254 time=3.874 ms > 64 bytes from 199.72.47.254: icmp_seq=13 ttl=254 time=5.642 ms > 64 bytes from 199.72.47.254: icmp_seq=14 ttl=254 time=6.101 ms > 64 bytes from 199.72.47.254: icmp_seq=15 ttl=254 time=3.200 ms > 64 bytes from 199.72.47.254: icmp_seq=16 ttl=254 time=4.661 ms > 64 bytes from 199.72.47.254: icmp_seq=17 ttl=254 time=2.188 ms > 64 bytes from 199.72.47.254: icmp_seq=18 ttl=254 time=6.329 ms > 64 bytes from 199.72.47.254: icmp_seq=19 ttl=254 time=3.740 ms > 64 bytes from 199.72.47.254: icmp_seq=20 ttl=254 time=6.878 ms > 64 bytes from 199.72.47.254: icmp_seq=21 ttl=254 time=4.422 ms > > id say not a network problem, someone also mentions reverse DNS on the > ip and name, well they were not in dns, so i put them in dns but i still > have the same problem > > Majid Almassari wrote: > > > > It looks like a network problem to me. Due a ping and see how long does the > > ping take, also ping your DNS server it just might be taking a while till it > > reverse lookup the address. Try using FQDN if you have a nameserver > > specified. also do a traceroute to your DNS server see how many hops till > > you reach it and the delay associated. Hopefully that helps. > > > > > -- > Windows 95 (win-DOH-z), n. A thirty-two bit extension and graphical > shell to a sixteen bit patch to an eight bit operating system > originally coded for a four bit microprocessor which was used in a PC > built by a formerly two bit company that couldn't stand one bit of > competition. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?010c01bf33b4$335e2140$0e91ddd1>