×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
That 20x number might be your ISP or Internet Service Provider. Since we
have a few hundred users I have to rely on our internal DNS. Internally
we run those on Windows. I rely on our Windows to also store the ISP's
address or anything else they feel they need to in order to access the
outside world. So, in our CFGTCP I put the addresses of three different
windows servers all serving DNS. I do not put any ISP addresses in there.
So, why is the other guy's name resolution running slow? Could be
anything, but it may be because the number you put in there is your ISP
and not his. Therefore it has to go out on the internet all the way to
your ISP to get a name resolution. That could be a hit. Conspiracy
theorists might say that your ISP puts a higher priority on serving their
own customers first before others.
If the other person is claiming that they have their DNS fixed I'd try
dropping that new number and give it a go. From that i try
NSLOOKUP HOSTNAME(nra.org)
You should get something like
Here, 10.10.4.250 is one of our Windows based DNS servers. What this is
telling you is that we were able to get name resolution to nra.org by
using server 10.10.4.250.
Domain name server:
Internet address . . . . . . . '10.10.4.250'
Internet address . . . . . . . '10.10.4.252'
Internet address . . . . . . . '10.17.4.180'
The NSLOOKUP will also tell you if the slowdown is name resolution or
connection to the target ftp site.
To trace the connection to the target ftp site you could try:
TRACEROUTE RMTSYS(NRA.ORG) replacing nra.org with your target ftp site.
You can see how long individual hops take. It looks prettier if you do
CALL QCMD
F10=Include detailed messages
Then issue the TRACEROUTE
Hit F1 on each step and record the times.
09:16:21-TRACEROUTE RMTSYS(NRA.ORG)
09:17:10-Probing possible routes to NRA.ORG (64.29.201.96) using *ANY
interface.
09:17:10-1 gdslan-v1 (10.10.1.1) 0.965 0.646 0.670
09:17:10-2 gdswan-p1-9 (10.10.0.10) 0.212 0.203 0.236
09:17:10-3 inet-v1 (64.184.23.1) 0.793 0.385 0.335
09:17:10-4 64.184.0.130 16.8 16.2 16.9
09:17:17-5 208.103.45.46 13.9 14.6 14.2
09:17:17-6 12.117.231.185 21.7 21.6 21.5
09:17:17-7 cr83.cgcil.ip.att.net (12.122.133.22) 65.5 65.4 64.9
09:17:17-8 cr1.cgcil.ip.att.net (12.123.7.110) 63.4 64.0 63.5
09:17:17-9 cr1.cl2oh.ip.att.net (12.122.2.206) 64.9 65.6 65.1
09:17:18-10 cr2.nsvtn.ip.att.net (12.122.28.73) 64.2 63.5 63.4
09:17:18-11 cr1.nsvtn.ip.att.net (12.122.28.69) 67.6 68.1 66.7
09:17:18-12 cr2.attga.ip.att.net (12.122.28.105) 65.9 66.7 65.8
09:17:18-13 cr1.ormfl.ip.att.net (12.122.31.30) 63.6 63.6 63.7
09:17:19-14 gar4.miufl.ip.att.net (12.122.143.53) 64.8 64.9 65.0
09:17:19-15 12.88.168.14 154 154 154
09:17:20-16 66.165.161.230 184 182 183
09:17:21-17 66.165.160.98 190 190 191
09:17:22-18 daa.g920.ispa.datareturn.com (64.29.192.197) 182 182 182
09:17:23-19 daa.g906.p40a.datareturn.com (64.29.192.213) 191 191 190
09:17:24-20 port-64-1952096-da120383www001.d (64.29.201.96) 182 181 182
You can see that it took 39 seconds to perform name resolution.
The individual hops ranged from subsecond to 7 seconds.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
