Dreamhost routing issues since 2017/02/17

Moderator: GSH

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Dreamhost routing issues since 2017/02/17

Post by Commando » Sun Feb 19, 2017 10:36 pm

Has the site's up address changed?

The site fails to load from my LAN but it loads from my phone.

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: b132ak posted

Post by Commando » Sun Feb 19, 2017 11:02 pm

It appears the same so it isn't a dns issue.

It appears I can't reach apache2 on my connection.

It responds over the vpn.

User avatar
Red Devil
Recycler
Posts: 4395
Joined: Fri Feb 18, 2011 5:10 pm
Location: High in the Rocky Mountains

Re: b132ak posted

Post by Red Devil » Sun Feb 19, 2017 11:36 pm

i can reach them okay via my pc browser; slow, though.

maint scheduled tomorrow:

https://www.dreamhoststatus.com/
If given the truth, the people can be depended upon to meet any national crisis. The great point is to bring them the real facts - and beer.
Abraham Lincoln

Battlestrat, FE, G66, In The Shadows, Starfleet, Uler, & ZTV

Lifetime member of JBS and NRA

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: b132ak posted

Post by Commando » Mon Feb 20, 2017 1:33 am

Over my cox connection, I haven't been able to reach the site since yesterday.

If I use cellular or my work vpn, I can reach the forums.

Both resolve to the correct up.

On my cox connection, it times out when it tries to ping the apache2 server, which is the host of both the forums and the matchmaking sites.

I posted my trace routes on the management board.

As of now, neither the forums and matchmaking work for me.

I doubt I can reach the ftp host to download beta patches either.

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: b132ak posted

Post by Commando » Mon Feb 20, 2017 1:37 am

I can't tell if the issue is on my end or dreamhost's end.

It behaves as if my ip has been blocked.

User avatar
squirrelof09
Sabre
Posts: 280
Joined: Sat Feb 19, 2011 3:00 am
Location: ts3.theothergamers.org
Contact:

Re: b132ak posted

Post by squirrelof09 » Mon Feb 20, 2017 1:58 am

I was having issues yesterday myself.

User avatar
Red Devil
Recycler
Posts: 4395
Joined: Fri Feb 18, 2011 5:10 pm
Location: High in the Rocky Mountains

Re: b132ak posted

Post by Red Devil » Mon Feb 20, 2017 2:56 am

tried ipconfig /flushdns?
If given the truth, the people can be depended upon to meet any national crisis. The great point is to bring them the real facts - and beer.
Abraham Lincoln

Battlestrat, FE, G66, In The Shadows, Starfleet, Uler, & ZTV

Lifetime member of JBS and NRA

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: b132ak posted

Post by Commando » Mon Feb 20, 2017 2:59 am

It's not a dns issue.

It resolves to the correct IP address.

User avatar
GSH
Patch Creator
Posts: 2458
Joined: Fri Feb 18, 2011 4:55 pm
Location: USA
Contact:

Re: Dreamhost issues 2017/02/17..20

Post by GSH » Mon Feb 20, 2017 3:46 pm

I posted a support ticket w/ Dreamhost yesterday (Sunday 2/19). Seems better now, but only from certain connections. Not sure why this happened.

-- GSH

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: Dreamhost issues 2017/02/17..20

Post by Commando » Mon Feb 20, 2017 3:54 pm

Pulled up my router's interface, remotely.

Tried pinging bzforum.matesfamily.org.

Still 100% packet loss.

Hopefully it is getting looked into.

User avatar
GSH
Patch Creator
Posts: 2458
Joined: Fri Feb 18, 2011 4:55 pm
Location: USA
Contact:

Re: Dreamhost issues 2017/02/17..20

Post by GSH » Mon Feb 20, 2017 4:08 pm

Hm. Not quite resolved yet. My work computer connects fine. Home doesn't. I can connect from work computer -> home, but not the reverse.

Many sites disable pings for reduced load, etc. I use a text webbrowser ( lynx http://bzforum.matesfamily.org ) to verify things. That's a lot more heavyweight of a connection than a ping, but is what is essentially what all web-browsers will do and use.

-- GSH

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: Dreamhost issues 2017/02/17..20

Post by Commando » Mon Feb 20, 2017 4:51 pm

Pings work from my work network, so that isn't the case.

I have a tracert on the Access thread, right below this one.

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: Dreamhost issues 2017/02/17..20

Post by Commando » Mon Feb 20, 2017 4:53 pm

My Trace Routes (TRACERT) from yesterday.

From work, when I ping 173.236.227.112, I get replies. When I ping the same IP from home, it times out.

I also get replies from my cell phone, over LTE. Over WiFi, I time out like my pc.

I can browse the forums over my phone or over my work vpn.

From my home network, I can't load the page.

Code: Select all

Tracert Results over VPN

Tracing route to bzforum.matesfamily.org [173.236.227.112]
over a maximum of 30 hops:

  1    50 ms    51 ms    48 ms  192.168.199.63
  2    50 ms    49 ms    51 ms  192.168.199.254
  3    49 ms    52 ms    49 ms  192.168.199.1
  4    57 ms    52 ms    50 ms  okcedge2.boithostedservices.com [71.146.224.4]
  5    62 ms    61 ms    65 ms  kanc-b1-link.telia.net [62.115.149.249]
  6    71 ms    71 ms    72 ms  dls-b21-link.telia.net [213.155.130.178]
  7    65 ms    67 ms    67 ms  abovenet-ic-311233-dls-b21.c.telia.net [62.115.55.202]
  8    65 ms    66 ms    65 ms  ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
  9   123 ms    97 ms    99 ms  ae27.cs2.dfw2.us.eth.zayo.com [64.125.30.182]
 10    95 ms    95 ms   111 ms  ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102]
 11    96 ms    98 ms   116 ms  ae3.cs2.dca2.us.eth.zayo.com [64.125.29.44]
 12    94 ms    93 ms    93 ms  ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249]
 13    96 ms    95 ms    94 ms  ae15.er5.iad10.us.zip.zayo.com [64.125.31.42]
 14    95 ms    95 ms    94 ms  208.185.23.134.t00867-03.above.net [208.185.23.134]
 15   104 ms    98 ms   100 ms  ip-208-113-156-4.dreamhost.com [208.113.156.4]
 16   104 ms   101 ms   102 ms  ip-208-113-156-14.dreamhost.com [208.113.156.14]
 17    98 ms   103 ms    94 ms  apache2-noxim.william-livingston.dreamhost.com [173.236.227.112]

Trace complete.
Tracert results from home

Code: Select all

Tracing route to bzforum.matesfamily.org [173.236.227.112]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2    22 ms    24 ms    22 ms  10.35.192.1
  3    21 ms    22 ms    22 ms  COX-68-12-9-56-static.coxinet.net [68.12.9.56]
  4    21 ms    24 ms    22 ms  COX-68-12-9-174-static.coxinet.net [68.12.9.174]
  5    33 ms    33 ms    32 ms  dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
  6    37 ms    38 ms    38 ms  68.105.30.22
  7    35 ms    34 ms    32 ms  ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
  8    72 ms    70 ms    70 ms  ae27.cs2.dfw2.us.eth.zayo.com [64.125.30.182]
  9    74 ms    74 ms    73 ms  ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102]
 10    75 ms   116 ms    77 ms  ae3.cs2.dca2.us.eth.zayo.com [64.125.29.44]
 11    68 ms    71 ms    73 ms  ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249]
 12    70 ms    69 ms    69 ms  ae15.er5.iad10.us.zip.zayo.com [64.125.31.42]
 13    71 ms    87 ms    71 ms  208.185.23.134.t00867-03.above.net [208.185.23.134]
 14    73 ms    77 ms    72 ms  ip-208-113-156-4.dreamhost.com [208.113.156.4]
 15    77 ms    75 ms    77 ms  ip-208-113-156-14.dreamhost.com [208.113.156.14]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.

User avatar
squirrelof09
Sabre
Posts: 280
Joined: Sat Feb 19, 2011 3:00 am
Location: ts3.theothergamers.org
Contact:

Re: Dreamhost issues 2017/02/17..20

Post by squirrelof09 » Mon Feb 20, 2017 5:11 pm

routing issues.

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: Dreamhost issues 2017/02/17..20

Post by Commando » Mon Feb 20, 2017 5:16 pm

That's what it looks like.

The question is whether it is on Cox's end or Dream Host's end though.

Oddly enough, it worked until Saturday.

Post Reply