Roller NetworkDue to popular demand all new colocations may have up to a 45 day lead time for scheduling an installation. All requests will be fulfilled in the order a colocation quote is signed. We apologize for the inconvenience, but we look forward to serving everyone as quickly as possible. Thanks!
Emergency and temporary colocation services will be unavailable until further notice.
We’ve released DNSSEC support for Primary DNS zones. This change marks a major new feature release after several months of work. As this is the initial public release, please let us know if you find any bugs we’ve missed or have any suggestions on how to improve it.
We added some additional checking in our system to mail forwarding for the case where a forward with an email address destination resolved to another forward to a mail box within the same hosted domain name was disabled. This was observed causing a mail loop for hosted mail domains in some cases. Our fix was to add additional logic to check another level of validity only when a mail domain is in “hosted” mode.
The cost of raw Internet bandwidth has plummeted over the last decade, and when you’re Google, it is even cheaper. When Google announced their fiber project, they initially claimed their network would be open to other providers. When Kansas City launched, they quietly retracted that. Even though Google is promising a number of upgrades to iProvo, having a government sanctioned monopoly for $1 is a sweet deal that would have never been offered to a local provider like XMission.
Read the full post at: http://transmission.xmission.com/2013/04/18/the-1-fiber-optic-network
Only a portion of the “172” and the “192” address ranges are designated for private use. The remaining addresses are “public,” and routable on the global Internet.
From: https://www.arin.net/knowledge/address_filters.html
In August 2012, ARIN began allocating “172” address space to internet service, wireless and content providers. There have been reports from the community that many network operators are denying access to devices having IP addresses from within the entire 172 /8 range. As a result, any device with a 172.x.x.x IP address may have difficulty reaching some sites on the global Internet. The only way to solve this problem is for those operators to reconfigure their router or firewall access control and filter only address space from the 172.16.0.0 /12 range.