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.
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.
We’re making changes in our network core by changing the MTU to 9216 (from 9000). We don’t anticipate any impact, but as always, contact us if anything seems odd. 9216 is the lowest common denominator MTU across our various routers.
Colocation customers taking advantage of jumbo frame support should continue to use an MTU of 9000 for Ethernet interfaces connected to our infrastructure.
Effective immediately, Rollernet will discontinue use of the dnsbl.njabl.org DNSBL zone due to its shutdown. We’re also removing it from all custom settings.
March 1, 2013: NJABL is in the process of being shut down. The DNSBL zones have been emptied. After “the Internet” has had some time to remove NJABL from server configs, the NS’s will be pointed off into unallocated space to hopefully make the shutdown obvious to those who were slower to notice.