posted by
NCommander
on Tuesday April 01 2014, @12:00PM
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.
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.
No, and the design of slash makes it extremely tricky to have a subdomain point to the main site and make it work because of the use of absolute addresses *everywhere*. The dev site has IPv6 records and we're using that to experiment with. Once we have the known IPv6 bugs extinguished, we'll publish AAAA records on the main site.
(Score: 1) by egp on Tuesday April 01 2014, @07:16PM
Often websites that are experimenting with IPv6 will have an address like ipv6.soylent.org that is reachable only by IPv6. Do we have one setup yet?
(Score: 2) by NCommander on Sunday April 06 2014, @03:01PM
No, and the design of slash makes it extremely tricky to have a subdomain point to the main site and make it work because of the use of absolute addresses *everywhere*. The dev site has IPv6 records and we're using that to experiment with. Once we have the known IPv6 bugs extinguished, we'll publish AAAA records on the main site.
Still always moving