Slash Boxes

SoylentNews is people

posted by NCommander on Tuesday April 01 2014, @12:00PM   Printer-friendly
from the there-was-much-rejoicing dept.
As part of wanting to be part of a brighter and sunny future, we've decided to disconnect IPv4 on our backend, and go single-stack IPv6. Right now, reading to this post, you're connected to our database through shiny 128-bit IP addressing that is working hard to process your posts. For those of you still in the past, we'll continue to publish A records which will allow a fleeting glimpse of a future without NAT.Believe it or not, we're actually serious on this one.

Linode IPv6 graph

We're not publishing AAAA records on production just yet as Slash has a few minor glitches when it gets an IPv6 address (they don't turn into IPIDs correctly), though we are publishing an AAAA record on dev. With one exception, all of our services communicate with each other on IPv6.

Perhaps I will write an article about our backend and the magical things that happen there :-).
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by alioth on Tuesday April 01 2014, @01:16PM

    by alioth (3279) on Tuesday April 01 2014, @01:16PM (#24122)

    ...and get the front end also with AAAA records. I've had an IPv6 address at home and at work for years now. Services to allow teenagers to share selfies (Facebook) have a working IPv6 front end, it's silly that a *tech* site does not! (And that goes for slashdot too. Years of writing articles about IPv6 and they still don't support it either).

  • (Score: 2) by xlefay on Tuesday April 01 2014, @01:20PM

    by xlefay (65) on Tuesday April 01 2014, @01:20PM (#24126) Journal

    As mentioned before, Slash takes issue with IPv6, we're looking to fix that. And with 'we' I mean, NCommander and others.

  • (Score: 3, Informative) by NCommander on Tuesday April 01 2014, @01:25PM

    by NCommander (2) Subscriber Badge <> on Tuesday April 01 2014, @01:25PM (#24131) Homepage Journal

    We're publishing one on dev right now, and I'm going to go through the DNS and make sure we have them on all other services aside from production

    From dig: ;; ANSWER SECTION: 300 IN AAAA 2600:3c00::f03c:91ff:fe6e:d0a3

    I hope to have IPv6 up by the end of the month; I've got a good idea on how to fix the problems with slash when it receives a 128-bit address.

    Still always moving