Sites not answering on IPv6


#1

I am not a customer of DreamHost, but a number of my friends and associates are. I have discovered a number of their sites have IPv6 addresses, but are not answering over same.

The list of sites I have discovered having this problem at present:
chris-cline.com (first discovered on 10 October 2014)
jellybabiescantrunawaywhenyoubiteofftheirlegs.co.uk (17 Nov 2014)
sadukie.com
codinggeekette.com
clevelandtechevents.com
daytontechevents.com
cletechconsulting.com
qtlil.me

If there are other sites exhibiting these symptoms, please reply to this post with the URL.

To reproduce the problem:
kjotte@daedalus:~$ curl -Iv6 http://chris-cline.com/

  • Hostname was NOT found in DNS cache
  • Trying 2607:f298:4:141::c0c:1e7a…
  • connect to 2607:f298:4:141::c0c:1e7a port 80 failed: No route to host
  • Failed to connect to chris-cline.com port 80: No route to host
  • Closing connection 0
    curl: (7) Failed to connect to chris-cline.com port 80: No route to host

Back in September I discovered a friend’s site (iamduke.com) exhibiting the same symptoms. This problem was resolved with ticket #94748597. Another customer saw this problem and filed tickets 8463 96219357 (9 Nov) 8463 96260240 (10 Nov) to no avail.

It’s been over two years since World IPv6 Launch. IPv6 is production now. Having sites unavailable to a significant portion of the Internet for over a month is deplorable. It appears that DreamHost is not monitoring their own infrastructure for these defects. Customers of their customers should not detect these problems before DreamHost. See: http://blog.flyingpenguintech.org/2014/05/monitor-your-ipv6.html

I have gladly recommended DreamHost in the past because of its proactive position on IPv6. I am seriously reconsidering that recommendation.


#2

Adding ticket #6581117 to this list for this issue
[hr]
I have IPv6 tracert information available as well. Testing with sadukie.com, iamduke.com, and cletechconsulting.com, there are 3 different failure points. I can make these available to support if needed.


#3

Update, although not ideal…

" there is a current bug open with our admins regarding IPv6 and how it intermittently disconnects. They are working to resolve this but I’m afraid we have no ETA at this time."

There are times where I have to disable IPv6 to get some of my own developer tools to work. While I understand that it’s critical to get IPv6 figured out, there are a lot of implementations that need to get straightened out.

DreamHost - if you guys need an IPv6 expert on your side, Nivex is my IPv6 guru that I turn to when figuring out what’s going on with it.


#4

Here we are a year later and nothing has changed:

kjotte@daedalus:~$ curl -Iv6 http://sadukie.com/
*   Trying 2607:f298:1:126::6b0:d70d...
* connect to 2607:f298:1:126::6b0:d70d port 80 failed: No route to host
* Failed to connect to sadukie.com port 80: No route to host
* Closing connection 0
curl: (7) Failed to connect to sadukie.com port 80: No route to host
kjotte@daedalus:~$ curl -Iv6 http://qtlil.me/
*   Trying 2607:f298:1:126::2dd:1995...
* connect to 2607:f298:1:126::2dd:1995 port 80 failed: No route to host
* Failed to connect to qtlil.me port 80: No route to host
* Closing connection 0
curl: (7) Failed to connect to qtlil.me port 80: No route to host