I've taken a slightly different and more broad approach because the previous solution doesn't last when Crashplan randomly changes the backup URL.
I've got three servers on the Pro plan, and have gone through 5 URL changes since the UTM was deployed in November. On the most recently added server Crashplan has changed the destination URL twice in 3 days, so a new solution was in order.
I noticed all of the previous URLs I had been assigned were in the 162.222.4x.0 range.
I checked ARIN's network registration for Code42 and verified that they have been assigned the 162.222.40.0/21 block (162.222.40.0-162.222.47.255).
Therefore, I've added that entire /21 network an exception.
Since the central.crashplan.com and central.crashplanpro.com hostnames have both been used on my Pro plan in the past, I kept them both as separate DNS group entries.
In summary,
Go to Web Protection > Filtering Options > Misc tab
Add the following:
I've taken a slightly different and more broad approach because the previous solution doesn't last when Crashplan randomly changes the backup URL.
I've got three servers on the Pro plan, and have gone through 5 URL changes since the UTM was deployed in November. On the most recently added server Crashplan has changed the destination URL twice in 3 days, so a new solution was in order.
I noticed all of the previous URLs I had been assigned were in the 162.222.4x.0 range.
I checked ARIN's network registration for Code42 and verified that they have been assigned the 162.222.40.0/21 block (162.222.40.0-162.222.47.255).
Therefore, I've added that entire /21 network an exception.
Since the central.crashplan.com and central.crashplanpro.com hostnames have both been used on my Pro plan in the past, I kept them both as separate DNS group entries.
In summary,
Go to Web Protection > Filtering Options > Misc tab
Add the following: