Lobsters currently lacks support for IPv6. What barriers are in the way for dual stacking the website?
The ISP hosting the server this site runs on doesn’t yet offer IPv6. I’ve asked them every year for the past three or so, and they keep saying they’re working on it. IPv6 isn’t a priority for me either, though, so I’m not going to drop them just because of it.
;; QUESTION SECTION:
;lobste.rs. IN AAAA
;; AUTHORITY SECTION:
lobste.rs. 3576 IN SOA ns1.superblock.net. hostmaster.superblock.net. 2014020301 3600 1800 604800 7200
No answer section :-(
There’s other providers; but if your datacenter does not provide ipv6 yet you will need to just tunnel it in.
Most give you a /64 to start with; that’s a lot of ip’s to work with. If you’re talking just a vps this should be doable; the scripts on tunnelbroker.net should help you set everything up.
For reliability, I’ve had significantly better results with SixXS than with HE.net’s tunnel services. Test thoroughly either way, of course.
journeysquid, I think that depends on your endpoint entirely. I have had the opposite experience with SixXS.
I was a SixXS user starting in 2006. I previously used HE.net but I changed due to their fire-walling policies that have since changed.
Let me start by saying SixXS uses credits (or did). So you sign up and you request a tunnel and after 2-3 weeks of having your tunnel up you have saved up enough credits to ask for another tunnel; or a /48. I was naive I did not understand the stupidity of this; virtual currency basically but you cannot buy any credits.
So having pops go down from time to time; you get docked credits; it costs you credits to change your pop (and you get a new ip allocated sometimes). I found this behavior to be harmful to the consumer (me) and pointless so I went back to he.net where they gave me everything i wanted without making me wait 3 weeks; or save up credits or nag me when my isp is down for a day.
I do hope that SixXS has become better since then; but looking back it’s like some kind of virtual currency sham to penalize (me) for wanting ipv6.
SixXS is the reason I’m asking my ISP for a native address; my tunnel goes down very frequently. I’d say once a week or so. That might not seem like a lot, but it causes quite a bit of disruption. Enough to move my home server off my network and to disable IPv6 on most of my devices. Once the ball was rolling it wasn’t long till I was disabling AICCU on my router. It’s very disruptive to try SSHing into a server and have it fail because I’m using an IPv6 address and my tunnel is down. Again.
Maybe you had better results but SixXS disappointed me quite a bit. Also, once I saw connectivity problems, I’d sign in and see the tunnel in green; it seems the system rarely detected any problems but I could see multi hour long outages on the graphs; all would fall to zero.
I’d like to try HE at some point but I’ve been using a tunnel for around a year now. My ISP should be implementing native IPv6.
Not sure if this could be an option.
[Comment removed by author]
I don’t think that’s true. It’s hosted by jcs on some sort of realish server.
I am mistaken. I’ll delete my comment to prevent the spread of misinformation.