Where does my domain point to for YOU?

Miscellaneous Topics
#1

We’ve been caught out by a hosting company that started out good, has gone evil (hostway - don’t touch with a barge pole). They got us on the spam blacklist, wouldn’t take any action to get off, etc. We’ve moved to a new provider, who we’d been using to host games for a while, but the old one seems to still be causing problems.

Some people’s browsers are picking up a bizarre mapping of grexengine.com to an address run by “GX Networks” (62.232.130.12) whom I’ve never heard of, and finds a “clone” of our website that is partially out of date, and is returning 403 forbidden on other pages.

Curious situation whereby Mozilla resolves to this 3rd party, whilst manual telnet port 80 connections to grexengine.com automatically resolve correctly to 1and1 (212.227.127.227) where our website is correct, up-to-date, etc.

I’d like to find out what “ping grexengine.com” points to for people outside of our LAN - if the problems are local only, then that’s annoying but OK. If not, we’ve got major problems :frowning:

#2

markus@alderaan:~$ ping grexengine.com
PING grexengine.com (212.227.127.227): 56 data bytes
64 bytes from 212.227.127.227: icmp_seq=0 ttl=57 time=62.4 ms

Seems to be correct :slight_smile:

#3

Same here, things seem dandy in the outside world :wink:

Kev

#4

So, basically, it looks like our gateway has picked up some weird DNS mapping.

Still, I think it just delegates to the ISP’s DNS servers (no local caching DNS, IIRC), which would suggest everyone else on the same ISP (nildram) could be affected…

Anyway, it’s enough to know that not everyone has this problem, so we can safely direct people to the site :).Thanks!

#5

Grexengine.com works fine for me:

C:\WINDOWS\Desktop>ping grexengine.com

Pinging grexengine.com [212.227.127.227] with 32 bytes of data:

Reply from 212.227.127.227: bytes=32 time=41ms TTL=51
Reply from 212.227.127.227: bytes=32 time=28ms TTL=51
Reply from 212.227.127.227: bytes=32 time=28ms TTL=51
Reply from 212.227.127.227: bytes=32 time=41ms TTL=51

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

And seems to display correctly in Mozilla 1.4. I can’t see a website at 62.232.130.12 at all, although it pings fine.

A trace route on those two addresses shows them going in totally different directions! I suspect you’ve got a duff DNS mapping somewhere that is confusing things.

#6

So, basically, it looks like our gateway has picked up some weird DNS mapping.

Well my router caches resolved DNS… so if your’s does the same it could explain it :wink:

Reboot it and you’ll see.

Got 212.227.127.227 too.

#7

Resolves correctly from a server I administer that lives at Nildram’s house, so I don’t think the problem is there.

#8

Mozilla wouldn’t receive emails (refused to even attempt to connect to server), so I killed and restarted it, and the DNS problem has vanished. Possibly, then, some mozilla caching problem (yes, I did flush the cache manually without fixing the problem ;)).

Rather sad that I had to copy/paste stuff from a couple of windows, and bookmark 100+ tabs so that I could restart the web-browser - because of whoever it was @ mozilla/netscape that decreed mozilla apps would NOT restart unless ALL were restarted at once - so this bug in the email client required me to shut down all browsers :(.