From: W on
Windows Update connects to anyone of hundreds of thousands of possible IP
addresses that match the general DNS name pattern:

a99-99-99-99.deploy.akamaitechnologies.com

Is there any way with Firewall-1 Next Generation to create a security rule
that passes all such hosts based on the domain name?

When I create the rule using either domain:

akamaitechnologies.com
deploy.akamaitechnologies.com

the rule does NOT match to the connection attempt.

I don't want to specify a network or address range since Akamai is used by
huge numbers of companies and I don't want a rule that is too permissive.
I'm hoping that they might at least restrict the
deploy.akamaitechnologies.com subdomain to a subset of all of their customer
uses. Is there any way to get Firewall-1 to pass traffic going to this
subdomain?

--
W