Is Eircom blocking sites?

kingbob387

Hai, I was just wondering is Eircom blocking certain sites from us.

Since I was trying to download off megaupload. http://www.megaupload.com/?d=18TN8TMO

But I found out that it isn't working, so I asked one of my friend online to try (he is in Britain) and it worked for him, so I am just asking does anyone else have that problem, or is it just me?


Btw, I asked my friend across the road to try it too, which didn't work for him and we are on the same Eircom package.

PCPhoto

worked for me ... magnet interweb

PogMoThoin

No problems for me on Eircom although the speed is limited to 450kB/s as I'm not a premium user

kingbob387

Weird, I can't get into it, getting a DNS error, but every other sites work!

DeVore

I'm on Eircom but I dont see a DNS entry for that domain.
WHOIS says it resides on 69.41.185.222 which I can tracert.

It could be something as simple as a DNS error (your mate might be getting a DNS entry while you and I (using eircom's DNS) arent).

Traffic is getting through to that IP though I guess they could be doing some HTTP traffic routing/shaping funny business...

DeV.

kingbob387

ok, what can I do?

PogMoThoin

I'm using OpenDNS instead of Eircoms crappy ones. I'm getting 67.215.65.132 on nslookup

jor el

Curiouser and curiouser. The IP changes with each ping.

C:\Documents and Settings\Jock>ping www.megaupload.com

Pinging www.megaupload.com [69.5.88.200] with 32 bytes of data:

Reply from 69.5.88.200: bytes=32 time=138ms TTL=53
Reply from 69.5.88.200: bytes=32 time=138ms TTL=53
Reply from 69.5.88.200: bytes=32 time=140ms TTL=53
Reply from 69.5.88.200: bytes=32 time=137ms TTL=53

Ping statistics for 69.5.88.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 137ms, Maximum = 140ms, Average = 138ms

C:\Documents and Settings\Jock>ping www.megaupload.com

Pinging www.megaupload.com [69.5.88.210] with 32 bytes of data:

Reply from 69.5.88.210: bytes=32 time=140ms TTL=53
Reply from 69.5.88.210: bytes=32 time=137ms TTL=53
Reply from 69.5.88.210: bytes=32 time=137ms TTL=53
Reply from 69.5.88.210: bytes=32 time=137ms TTL=53

Ping statistics for 69.5.88.210:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 137ms, Maximum = 140ms, Average = 137ms

C:\Documents and Settings\Jock>ping www.megaupload.com

Pinging www.megaupload.com [69.5.88.215] with 32 bytes of data:

Reply from 69.5.88.215: bytes=32 time=137ms TTL=53
Reply from 69.5.88.215: bytes=32 time=143ms TTL=53
Reply from 69.5.88.215: bytes=32 time=138ms TTL=53
Reply from 69.5.88.215: bytes=32 time=142ms TTL=53

Ping statistics for 69.5.88.215:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 137ms, Maximum = 143ms, Average = 140ms

Try changing DNS servers to Opendns:
208.67.222.222 and 208.67.220.220


This should also work for the URL you want:
http://69.5.88.200/?d=18TN8TMO

watty

I get
www.megaupload.com [69.5.88.224]

I guess it's a load sharing array of servers.

DeVore

Probably using DNS TTL as a quick and dirty load balancing solution (cheap gits )

Could that be why Eircom has dropped them?? Would be interesting if they were quietly dropping sharing sites from DNS....


DeV.

watty

Take that idea over here dev.

www.megaupload.com [69.5.88.211]

My router is using Digiweb DNS and OpenWRT.

It caches ARP and DNS for a while. So if I repeatedly ping with short gap the IP doesn't change. I have to ping after openWRt's cache has expired and then I see a new IP.

They should be using a reverse proxy load balancing and one IP not mucking with DNS?

kingbob387

That worked, but the actual website (as in www.megaupload.com) didn't work.

kingbob387

Sweet, thanks guys, OpenDns worked and www.megaupload.com works once again! Thank you guys SOOO much!

JimmyFloyd

Alot of people having trouble accessing Megaupload on Eircom.

Any news on this?

kingbob387

It's the DNS problemo, chnage your DNS settings to the OpenDns and everything will work perfectly, I changed to OpenDns and everything worked out