Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed

Outline · [ Standard ] · Linear+

 The "extreme Screamyx Slowdowns" V4, Edisi :Extreme International Slowdowns

views
     
andrew9292
post Jul 8 2009, 06:29 PM

-/Livin' On A Prayer/-
*****
Senior Member
955 posts

Joined: Sep 2008
From: Petaling Jaya


QUOTE(heLL_bOy @ Jul 8 2009, 06:20 PM)
after change dns will be fine?
*
DNS works to translate a web address into "internet language(IP address)", that is how the internet works basically, its a bunch of numbers. For example forum.lowyat.net in internet language is 210.5.46.17.

So if the DNS is not responding...means your computer's request for the DNS to process a web address will not get thru, thus u cant surf the web smoothly.

QUOTE
PING TM DNS
C:\Documents and Settings\Andrew>ping 202.188.0.133 -n 25

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=11ms TTL=247
Reply from 202.188.0.133: bytes=32 time=10ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=14ms TTL=247
Reply from 202.188.0.133: bytes=32 time=13ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 202.188.0.133: bytes=32 time=21ms TTL=247
Reply from 202.188.0.133: bytes=32 time=17ms TTL=247
Reply from 202.188.0.133: bytes=32 time=16ms TTL=247
Request timed out.
Request timed out.
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 202.188.0.133:
  Packets: Sent = 25, Received = 10, Lost = 15 (60% loss),
Approximate round trip times in milli-seconds:
   Minimum = 9ms, Maximum = 21ms, Average = 12ms


QUOTE
PING OPEN DNS
C:\Documents and Settings\Andrew>ping 208.67.222.222 -n 25

Pinging 208.67.222.222 with 32 bytes of data:

Reply from 208.67.222.222: bytes=32 time=213ms TTL=55
Reply from 208.67.222.222: bytes=32 time=243ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=214ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=206ms TTL=55
Reply from 208.67.222.222: bytes=32 time=210ms TTL=55
Reply from 208.67.222.222: bytes=32 time=216ms TTL=55
Reply from 208.67.222.222: bytes=32 time=235ms TTL=55
Reply from 208.67.222.222: bytes=32 time=210ms TTL=55
Reply from 208.67.222.222: bytes=32 time=206ms TTL=55
Reply from 208.67.222.222: bytes=32 time=234ms TTL=55
Reply from 208.67.222.222: bytes=32 time=207ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=214ms TTL=55
Reply from 208.67.222.222: bytes=32 time=205ms TTL=55
Reply from 208.67.222.222: bytes=32 time=242ms TTL=55
Reply from 208.67.222.222: bytes=32 time=214ms TTL=55
Reply from 208.67.222.222: bytes=32 time=205ms TTL=55
Reply from 208.67.222.222: bytes=32 time=243ms TTL=55
Reply from 208.67.222.222: bytes=32 time=206ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=235ms TTL=55
Reply from 208.67.222.222: bytes=32 time=205ms TTL=55
Reply from 208.67.222.222: bytes=32 time=211ms TTL=55

Ping statistics for 208.67.222.222:
  Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 205ms, Maximum = 243ms, Average = 217ms


WTF 60% loss to TM DNS and 0% loss to OPENDNS WTF WTF WTF WTF

This post has been edited by andrew9292: Jul 8 2009, 06:33 PM
andrew9292
post Jul 8 2009, 06:35 PM

-/Livin' On A Prayer/-
*****
Senior Member
955 posts

Joined: Sep 2008
From: Petaling Jaya


QUOTE(fabianz03 @ Jul 8 2009, 06:24 PM)
TM DNS fakap again!  rclxms.gif  rclxms.gif
*
QUOTE(fabianz03 @ Jul 8 2009, 06:30 PM)
Cool down Andrew... We know we know... It already happened once...
After that I stick with OpenDNS forever.
*
Maybe they not happy with /k/ army send complain letter to star vmad.gif vmad.gif vmad.gif vmad.gif vmad.gif
hahaha

same lah, i find that altho OpenDNS located oversea, it still respond faster than TM DNS dont you think so?


Added on July 8, 2009, 6:38 pm
QUOTE(heLL_bOy @ Jul 8 2009, 06:32 PM)
mine don't have problem
*
seems to be okay for now (6:38pm) ...but i still using OpenDNS no matter what, i used for 2 months already, not even 1 downtime.

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Andrew>ping 202.188.0.133 -n 10

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=10ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247

Ping statistics for 202.188.0.133:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 10ms, Average = 9ms
------------------------------------------------------------------------------------------------------

EDIT: 6:51pm.

I take the following back :
QUOTE
seems to be okay for now (6:38pm) ...but i still using OpenDNS no matter what, i used for 2 months already, not even 1 downtime.


now their DNS seems to be timing out again, very unstable, sometimes ok for a minute then down again.

This post has been edited by andrew9292: Jul 8 2009, 06:53 PM
andrew9292
post Jul 12 2009, 11:42 PM

-/Livin' On A Prayer/-
*****
Senior Member
955 posts

Joined: Sep 2008
From: Petaling Jaya


Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Andrew>ping 202.188.0.133

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Request timed out.
Request timed out.

Ping statistics for 202.188.0.133:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms

DNS AGAIN
andrew9292
post Jul 12 2009, 11:48 PM

-/Livin' On A Prayer/-
*****
Senior Member
955 posts

Joined: Sep 2008
From: Petaling Jaya


Guys, TM's primary DNS is having problems again, i've done 100 pings to the DNS with 18% loss.

Please switch your DNS to OpenDNS, there is a a guide on how at a pinned thread in this forum.
http://forum.lowyat.net/topic/1056248

» Click to show Spoiler - click again to hide... «


This post has been edited by andrew9292: Jul 12 2009, 11:48 PM
andrew9292
post Jul 14 2009, 04:30 PM

-/Livin' On A Prayer/-
*****
Senior Member
955 posts

Joined: Sep 2008
From: Petaling Jaya


QUOTE(reddevils500 @ Jul 14 2009, 04:26 PM)
Aiyoh! Can't surf Google now.
Youtube gets lots of timed out pings.

TMNutz screwed up DNS again?  shakehead.gif
*
I was using OpenDNS, same problem, P1 Wimax DNS same problem, apa lagi TM DNS... rclxub.gif

I guess it's a international link issue

3 Pages < 1 2 3Top
Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0171sec    0.51    7 queries    GZIP Disabled
Time is now: 12th December 2025 - 06:39 AM