Connectivity issue with FQ datacenter???

[johnfl68]

Is there a problem with connectivity to the FQ datacenter???

I can not reach any of my FQ hosted domains, or those of my clients.

Here is a traceroute if it is of any help:

Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\John>tracert mydomain.com

Tracing route to mydomain.com [67.215.xx.xxx]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 192.168.2.1
3 44 ms 44 ms 44 ms fl-71-1-xxx-x.dhcp.embarqhsd.net [71.1.xxx.x]
4 44 ms 44 ms 44 ms crflwnpk02 [65.41.11.109]
5 44 ms 44 ms 44 ms host53.embarqservices.net [205.245.9.53]
6 44 ms 44 ms 44 ms te-7-2.car2.Orlando1.Level3.net [4.79.118.177]
7 44 ms 44 ms 44 ms ae-2-9.bar2.Orlando1.Level3.net [4.69.133.70]
8 44 ms 44 ms 44 ms ae-0-11.bar1.Orlando1.Level3.net [4.69.137.145]

9 53 ms 53 ms 53 ms ae-8-8.ebr1.Atlanta2.Level3.net [4.69.137.150]
10 63 ms 53 ms 54 ms ae-63-60.ebr3.Atlanta2.Level3.net [4.69.138.4]
11 74 ms 70 ms 69 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

12 77 ms 69 ms 70 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.1
34]
13 262 ms 211 ms 220 ms ae-23-79.car3.Washington1.Level3.net [4.68.17.69
]
14 88 ms 69 ms 69 ms SPLICE-COMM.car3.Washington1.Level3.net [4.79.16
8.118]
15 70 ms 70 ms 70 ms hit-servfail.opendns.com [67.215.xx.xxx]

John

[Kevin]

That is not a FutureQuest IP.

However, there is a problem and we are working on it.

[johnfl68]

Yes it is a FQ IP, I hid the last part of the IP with x's and the last stop (15 hit-servfail.opendns.com [67.215.xx.xxx]) went to openDNS because it would not route to FQ. All the FQ site IP's I tried routed the same.

If there is a known issue - why hasn't anyone from FQ posted about this?

John

[Terra]

That ended up being me... :(

I was adding a policy route and ended up breaking netfilter's state machine...

The rules have been reverted and everything is flowing properly again...

My apologies for the mishap and I will be researching why netfilter went catatonic with such a simple and innocuous change...

[johnfl68]

Thank you Terra for the update, we all make mistakes, this is understandable.

It's just a bit frustrating to have clients call with email problems as well as their sites are down, and I find the same for me, but find nothing posted here.

One of the reasons I like FutureQuest is because you let us know what is going on right away when there are problems. I hope that this will continue to be the case.

John

[Kevin]

Normally when something major goes wrong the techs work on the problem while someone else does a post. In this case we were still trying to figure out if it was a FutureQuest problem or a more general DNS problem when your question came in.

BTW, to dissect your particular situation with the non-FQ IP...

The problem is that we essentially firewalled off DNS traffic by accident. Your computer is apparently set to use OpenDNS instead of standard DNS. When OpenDNS can't resolve a host name to an IP address they provide you with a web page saying so instead of just a host not found error. When you did a traceroute it went to the IP address of the web server providing that page not your actual web server. So, that 67.215.x.x IP was not a FutureQuest IP but an OpenDNS IP which you went to because OpenDNS couldn't find your FutureQuest IP which even without looking I can tell you starts with a 69.

For the record, the problem lasted from 14:47 to 15:05 ET (the same minute as your post). However, due to the way that DNS is cached it started out a very small email only problem but then exploded into a much more general problem at about 14:55.