Skip to content
Little GolemMake your next move.

Little Golem inaccessible for some users after hardware migration

Public forum discussion.

General

#1 · cse85

9 Dec 2011

Hello Mr. Malaschitz,

the site seems to be inaccessible from some IPs since you migrated to new hardware. I tracerouted from two different IPs in Leipzig, Germany and they ended like this:

13 te1-4.ccr01.nue01.atlas.cogentco.com (130.117.49.70) 37.350 ms 40.993 ms 41.362 ms

14 te1-1.ccr01.drs01.atlas.cogentco.com (154.54.36.5) 46.487 ms te2-2.ccr01.drs01.atlas.cogentco.com (130.117.49.57) 41.576 ms 46.214 ms

15 te4-2.ccr01.prg01.atlas.cogentco.com (154.54.59.166) 48.841 ms 52.398 ms 52.770 ms

16 te3-8.mag01.prg01.atlas.cogentco.com (154.54.58.166) 53.152 ms 45.187 ms te3-1.mag01.prg01.atlas.cogentco.com (154.54.58.162) 49.399 ms

17 * * *

18 * * *

11 te2-2.ccr01.drs01.atlas.cogentco.com (130.117.49.57) 27.503 ms te1-1.ccr01.drs01.atlas.cogentco.com (154.54.36.5) 27.607 ms te2-2.ccr01.drs01.atlas.cogentco.com (130.117.49.57) 27.810 ms

12 te7-2.ccr01.prg01.atlas.cogentco.com (154.54.59.170) 35.177 ms te4-2.ccr01.prg01.atlas.cogentco.com (154.54.59.166) 31.112 ms te1-4.ccr01.prg01.atlas.cogentco.com (130.117.49.74) 35.187 ms

13 te3-1.mag01.prg01.atlas.cogentco.com (154.54.58.162) 228.153 ms te3-8.mag01.prg01.atlas.cogentco.com (154.54.58.166) 229.772 ms 228.136 ms

14 149.6.24.98 (149.6.24.98) 31.360 ms 31.104 ms 31.077 ms

15 * * *

16 * * *

The domain resolves to 81.2.209.236 in both cases, so DNS doesn't seem to be the problem. At the moment i'm accessing the site via a US-American web proxy, so it might be a routing issue. I'm not sure if my ISP is the culprit, but if not, it possibly affects other people.

I don't mind winning games because my opponents run out of time, but i think it would be unfair to take advantage of the situation and not report the issue.

Kind regards, Daniel.

#2 · MarleysGhost

10 Dec 2011

I couldn't reach LG for the last two days, from North America. I did look at the IP address that littlegolem.net was resolving too, and I don't recall it exactly, but it was at least substantially similar to "81.2.209.236".

#3 · Strange Yeah

10 Dec 2011

I also couldn't reach LG for two days, and I'm in Australia. Hopefully all is well now.

#5 · Aganju

10 Dec 2011

Same here, Florida. It is still extremely slow (45 secs per page).

Lost two vacation days :-(

#6 · cse85

10 Dec 2011

I didn't look hard enough. Maybe it is a DNS issue after all. From my home littlegolem.net resolves to 81.2.209.236 (a czech IP), from a canadian machine it resolves to 193.200.9.103 (a slovakian IP), which is www.axonpro.sk, a slovakian IT company.

Running 'wget --header="Host: www.littlegolem.net" 193.200.9.103' from the canadian machine gets me the Little Golem Homepage, after a redirect (302 Moved Temporarily), but doing the same from my home redirects me (once again 302) to 81.2.209.236, which times out.

'whois littlegolem.net' tells me their DNS is handled by a.dns.gandi.net, b.dns.gandi.net and c.dns.gandi.net, all three of which tell me that littlegolem.net resolves to 193.200.9.103.

So I guess 193.200.9.103 is the new IP, but the server still redirects me to the old IP, when accessed from my home.

#8 · MarleysGhost

10 Dec 2011

I agree. Now that it's working again, littlegolem.net resolves here to 193.200.9.103, which RDNS shows as hurin.axonpro.sk.

Perhaps your home is drawing from a cached entry kept improvidently long. [abc].dns.gandi.net are all showing TTL as 10800 seconds (3 hours).

#9 · Aganju

10 Dec 2011

DNS servers typically have the resolutions of names buffered up to 48 hours, are there are chain effects too. Axon Pro is the company Richard is working at.

Works now for me but still very slow.

#10 · cse85

13 Dec 2011

It seems to work now. But it's still somewhat funny, as I can reach LG through http://www.littlegolem.net as well as through http://81.2.209.236 , but their states are different.

I guess 81.2.209.236 is the old server (many games timed out, no activity in the forum). But I was slightly confused when I noticed it, because yesterday accessing http://www.littlegolem.net sent me nowhere, whereas http://81.2.209.236 worked, so I assumed the second one to be the correct server.

By the way, littlegolem.net resolves to 85.216.154.44 for me now, a slovakian IP.

#11 · vieuxsac

13 Dec 2011

I was traveling all over Europe last week; then back to the US in the weekend. I had problems accessing LG almost everywhere. It seems to be working fine now, except that I'm losing vacation days automatically. I had 50 hrs or so on the game that I had least time, and I just got a vacation day notification.

#12 · Richard Malaschitz

13 Dec 2011

I am sorry for problems. Server was two times moved. On Friday and on Sunday. It is in my kitchen now :)

#15 · bill

13 Dec 2011

hopefully it work soon as ive had trouble getting in alot

#17 · JerNYC

14 Dec 2011

Same with me and I also lost several vacation days.