|
| |
|
|
satimis
Posts: 1
Joined: 2/20/2006
Status: offline
 |
Proxy DNS can't be ping ? - 2/20/2006 11:00:15
Hi folks,
FedoraCore3
Firefox
==========
My PC, a workstation, is connected to 1.5Mb broadband via a ADSL modem then to telephone socket. Each time after connecting 2 nameservers were assigned;
# cat /etc/resolv.conf
nameserver 202.123.77.198
nameserver 202.123.77.203
(almost the same all the time on connecting)
Previously l complained to my ISP about the slow Internet browsing. After entering the URL on browser, clicked, I have to wait for prolonged time before the website displayed.
CLICK ---> RELAX ---> WAIT
My ISP requested me to re-set the config of the browser even sending technical staff making on site cable checking but could not discover the cause, only blaming I was running Linux OS with Firefox as browser which they won't support. Their reference standard is Internet Explorer on MSWindows.
Late I discovered the primary nameserver 202.123.77.198 having problem.
# ping -c 3 202.123.77.198 (*** Tested on Linux Desktop PC)
PING 202.123.77.198 (202.123.77.198) 56(84) bytes of data.
--- 202.123.77.198 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
After several complaints made, my ISP assigned another nameservers
# cat /etc/resolv.conf
202.123.77.196 (Primary nameserver)
202.123.77.203 (Secondary nameserver)
The primary nameserver 202.123.77.196 still had problem, failed on “ping” and “traceroute” tests.
# ping -c 3 202.123.77.196
PING 202.123.77.196 (202.123.77.196) 56(84) bytes of data.
From 202.123.95.82 icmp_seq=0 Time to live exceeded
From 202.123.95.82 icmp_seq=1 Time to live exceeded
From 202.123.95.82 icmp_seq=2 Time to live exceeded
--- 202.123.77.196 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2002ms, pipe
It indicated 100% packet loss.
Tested on server on Internet, run by "traceroute.org"
Version: v1.0 Date: 22-Jan-2002
Tracing route to 202-123-77-196.ihenderson.com [202.123.77.196]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 202.85.152.2
2 <10 ms <10 ms <10 ms ge1-2-cosw0907.hk01.iadvantage.net [202.85.129.50]
3 57 ms 235 ms 223 ms henderson-rge.hkix.net [202.40.161.105]
4 2 ms 2 ms 2 ms 202-123-94-91.ihenderson.com [202.123.94.91]
5 2 ms 2 ms 2 ms 202-123-94-51.ihenderson.com [202.123.94.51]
6 2 ms 2 ms 2 ms 202-123-95-82.ihenderson.com [202.123.95.82]
7 2 ms 2 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
8 2 ms 2 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
9 2 ms 3 ms 2 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
10 2 ms 2 ms 2 ms 202-123-95-82.ihenderson.com [202.123.95.82]
11 3 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
12 2 ms 2 ms 2 ms 202-123-95-82.ihenderson.com [202.123.95.82]
13 2 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
14 3 ms 3 ms 2 ms 202-123-95-82.ihenderson.com [202.123.95.82]
15 3 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
16 3 ms 2 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
17 2 ms 3 ms 2 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
18 2 ms 2 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
19 3 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
20 3 ms 2 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
21 3 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
22 3 ms 3 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
23 4 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
24 3 ms 3 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
25 3 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
26 3 ms 3 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
27 4 ms 5 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
28 4 ms 3 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
29 3 ms 3 ms 3 ms hdc-coreb-fe110.ihenderson.com [202.123.95.81]
30 3 ms 3 ms 3 ms 202-123-95-82.ihenderson.com [202.123.95.82]
Trace complete.
HTTP/1.1 502 Gateway Error
Server: Microsoft-IIS/5.0
Date: Thu, 09 Feb 2006 05:51:23 GMT
Connection: close
Content-Length: 186
Content-Type: text/html
The above indicated gateway error. It was found bouncing between 2 (two) routers, I suppose, similar to playing tennis.
Then later my ISP assigned AGAIN another new nameservers. Both went through “ping” and “traceroute” tests and the problem of slow Internet browsing disappeared.
Today my ISP on his email in reply to my complaints said that 202.123.77.196 (primary nameserver) belongs to Proxy DNS. Therefore, the Firewall will block the IP so that I cannot get any success result on the ping test. For 202.123.77.213 and 202.123.77.209 (the final nameservers assigned by them), they are not Proxy DNS, and therefore I can find the result on the ping test.
I fail to understand why some nameservers belonging to Proxy DNS behind firewall, as my ISP claimed, another not belonging to Proxy DNS without firewall protection. Why “traceroute” test on 202.123.77.196 showed “HTTP/1.1 502 Gateway Error”? If only because of non Proxy DNS which was/is not the cause of slow Internet browsing why my ISP finally re-assigned another new set of nameservers? Only to satisfy my curiosity on pinging the nameservers?
Besides I haven't reported to them both "202.123.77.213 and 202.123.77.209" went through "ping" and "traceroute" tests.
Please help me to understand my ISP's explanation. TIA.
B.Regards
satimis
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
