Roller NetworkDue to a large wave of spam account registrations on our forums over the last few weeks we have been forced to disable new user registrations. Sorting through large numbers of spam accounts to delete them is simply not a productive use of our time.
If you would like a forum account please contact technical support and we can create one for you. We apologize for the inconvenience.
We set up our first IPv6 native residential end user today. Although Roller Network has offered IPv6 services for some time now, it is not a high demand item for end users. If you happen to be in Reno, NV (or Sparks, NV and possibly Carson City, NV) and we can reach you and you want native IPv6, contact us.
The installation was over fixed wireless with a MikroTik RB750 (running 5.0b7 firmware) at the customer site. Both IPv4 and IPv6 are available natively (dual stack).
Just over a month ago we posted a video of our generator and transfer switch running through the self test process. These two videos show what happens in the UPS room when the transfer switch does its thing. But what happens with the UPS? The first video shows the corresponding UPS actions when the transfer switch moves from utility to generator.
The UPS will go to battery briefly as the transfer (although we don’t see any effect in the room lights) is enough to be momentarily out of tolerance. This is good: the transfer switch will reconnect under minimal load, extending its life and reducing the risk of a contact becoming fused. The generator test runs for an hour, so after that hour is up the transfer switch moves back to utility power from generator. This second video shows the actions of the UPS during the second half of this process.
As you can see, we perform a true test of our emergency power systems with confidence in its operation since a utility outage is identical to our test procedure. During a real utility outage the only major difference is that the UPS would run on battery from 10 to 20 seconds longer while the generator goes through its self start procedures before a transfer.
Our request to the registry for IPv6 glue records for the following name servers has been completed:
ns1-auth.rollernet.us 2607:fe70:0:3::c ns2-auth.rollernet.us 2607:fe70:0:4::c ns1.rollernet.us 2607:fe70:0:3::b ns2.rollernet.us 2607:fe70:0:4::b ns1-i.rollernet.us 2607:fe70:0:3::10 ns2-i.rollernet.us 2607:fe70:0:4::10
Earlier this month we posted a Sprint maintenance notice and hinted at a larger announcement. This event set the stage for this announcement: complete IPv6 support for our portfolio of services. Sprint needed to install a software upgrade on the router we’re connected to in order to offer dual-stack native IPv6 to our existing circuit. On December 21 we established an IPv6 BGP session to AS1239 and turned off our last tunnel.
We are pleased to announce that we are the first (and only as of this date) service provider in the state of Nevada that operates a legacy-free network that is 100% dual-stack native, including all of our transit providers and peers. Roller Network no longer operates any IPv4-only circuits (or tunnels) and it is our policy to require native IPv6 on any new upstream or peer. Native IPv6 is available to customers of all services levels, from our classic Mail and DNS accounts through colocation, dedicated servers, hosting and internet access to both businesses and residential users. There is no additional cost or special requests required for IPv6 support.
We’re also excited to begin offering IPv6 on our inbound mail service. Effective immediately, we are publishing concurrent A/AAAA records for mail.rollernet.us and mail2.rollernet.us with the servers behind host MX records capable of receiving mail via IPv6 and sending it to IPv6 destinations. This includes, but is not limited to, the popular Secondary MX and SMTP Redirection services.
Throughout the last year we have enabled IPv6 on a multitude of our services: DNS, outbound mail (smarthost/submission), hosted mail boxes (POP3, IMAP), colocation, hosting, and even our webmail. This final step of transitioning to all native transit and supporting IPv6 on the incoming mail component opens the door to an IPv6 future in 2011 and beyond.