From work, no problem. From phone, works if I'm not on my home WLAN.

I'm not sure where else to look -- I haven't change anything. Nslookup appears to work, so I'm not sure where else to look. I am running ipv6 so I don't have to deal with NAT issues, could that be it?

We're having the same issue at home. It works if we add the "www." for some reason. Brick is already looking into it.

by "looking into it' means i'm kinda annoyed and not sure what to do about it.

brickfungus wrote:

by "looking into it' means i'm kinda annoyed and not sure what to do about it.

I know the feeling.

As long as I remember to do add "www" as suggested by duce, I can survive. I think the only think that really breaks is the links from the shout box.

it's suddenly working for me...

what's your IP, i did a giant ip range ban when we were getting hit

are you on your phone using "internet" instead of a normal browser??... cus brick sarge and ducke told me to "deal with it and download chrome if thats the case" while we were all in denver... J/fkin/s

204.210.201.210

single-step solution guaranteed to work or your money back:
1. leave ohio

Laughlyn wrote:

are you on your phone using "internet" instead of a normal browser??... cus brick sarge and ducke told me to "deal with it and download chrome if thats the case" while we were all in denver... J/fkin/s

Both are working for me. Seems like some ISPs have incorrect information for the A records. Not sure if hosting has ever changed for the site, but I would go into DNS settings and check to make sure that halowheelmen.com and http://www.halowheelmen.com both only have 1 A record listed, and that it's pointing to the right IP.

I just had this issue with Minecraft server, sometimes it would work and sometimes it wouldn't. Turns out there were 2 IPs listed, because I neglected to delete the old A record for that subdomain.

Edit:
Confirmed, looks like http://www.halowheelmen.com has 2 A records listed, unless this has something to do with CloudFlare:

RubbrDuckE wrote:

single-step solution guaranteed to work or your money back:
1. leave ohio

Laughlyn wrote:

are you on your phone using "internet" instead of a normal browser??... cus brick sarge and ducke told me to "deal with it and download chrome if thats the case" while we were all in denver... J/fkin/s

What's wrong with Ohio?

In reference to MC's write up, I use Google for DNS at present -- I can switch back to TWC for test purposes if that would help.

Mzoga wrote:

RubbrDuckE wrote:

single-step solution guaranteed to work or your money back:
1. leave ohio

Laughlyn wrote:

are you on your phone using "internet" instead of a normal browser??... cus brick sarge and ducke told me to "deal with it and download chrome if thats the case" while we were all in denver... J/fkin/s

What's wrong with Ohio?

In reference to MC's write up, I use Google for DNS at present -- I can switch back to TWC for test purposes if that would help.

My post was more in reference to the dns records for the site. I would imagine that Google's DNS are fine. My point was that the configuration on the domain points www.halowheelmen.com to 2 IP addresses. This could be a round robin design implemented by CloudFlare, but I'm not sure.

So, if I use a VPN extension to chrome, I can get in from my home network. Otherwise, I can't get in at all anymore, with or without the www.