Blocked sites giving 504 gateway timeout errors

Follow

mindustries

September 19, 2013 15:07

I read http://forums.opendns.com/comments.php?DiscussionID=6665

a) Blocked sites give timeout errors.

b) http://block.opendns.com/?url=www.example.org&ablock gives time out error.

c) nslookup -type=txt which.opendns.com. 208.67.222.222 gives 5.chi

d) Blocked sites loaded for a few tries in the beginning but has not worked since then. Any tips?

1

• 

  rotblitz September 19, 2013 16:21

  You're using the OpenDNS location in Chicago.  Is this far away from your general geographical location?

  Better open a support ticket, so that OpenDNS staff can look into it.

  0

  Comment actions Permalink
• 

  mindustries September 19, 2013 17:16

  Yes, we are located in ohio. I would assume that chicago wouldn't be a problem. I'll open a ticket as well. Thanks.

  0

  Comment actions Permalink
• 

  maintenance September 20, 2013 01:47

  Just as a point of reference, from Ohio, CHI was standard for me, but NYC, DFW, WDC always worked just fine. 

  0

  Comment actions Permalink
• 

  mindustries September 20, 2013 01:58

  can you specify the locale of the server you want to connect to ?

  0

  Comment actions Permalink
• 

  rotblitz September 20, 2013 06:29

  No, OpenDNS use Anycast technology.

  0

  Comment actions Permalink
• 

  mindustries September 20, 2013 20:02

  blocked pages are now loading fine. I guess with these intermittent 504 errors; you'd have to wait it out.

  0

  Comment actions Permalink
• 

  maintenance September 21, 2013 03:47

  That's pretty much it, you can get a 504 from any hop between you and the destination server. If it's persistent, you can open a ticket and OpenDNS may find the node responsible and contact someone. If it is like a caching server of theirs, they can address it directly.

  0

  Comment actions Permalink

Please sign in to leave a comment.