Yet Another FQDN Wildcard question :D

Question

Admittedly I have read a few posts, and I believe one was similar to mine but a few years old so I wanted to ask fresh \ check on the status 
 
 Is there yet any support for a wildcard FQDN beyond subdomains? I should wish to place the wildcard marker (or better yet a regex) in the middle 
 
 Ex scenario - a hosted service for a website has multiple URLs (2 known, 457382 unknown lol) to pull pictures from (for their own load balancing or redundancy etc) domain: myweb1.amazonaws.com myweb2.amazonaws.com and both happen to be in countries which i otherwise block 
 
 I want to create an exception in my overall Country Blocking FW rule to allow HTTP(80) and HTTPS(443) to Destination Networks myweb*(or regex).amazonaws.com - because in my scenario i know of myweb1 and myweb2 but i don't know if there are others, and also assume they follow the same format because most Amazon \ Azure hosted services do i would like the Country Blocking Destination network to be inclusive of the unknown 
 Thank you

LuCar Toni · Answer

As we use Wildcard in combination with DNS, we are only "in for it" or not. 
 Meaning: You can do *.sophos.com and if someone tries to catch an IP for community.sophos.com, we will catch this and use it. The only way to block / allow it, is by using a direct FQDN like community.sophos.com, which we naturally resolve directly by using DNS in the product. 
 You only will be able to allow *.amazonaws.com or not. Or the direct approach. 
 I am not sure, thinking about implementing such an approach, if this would be a valid use case (in terms of not being to overcomplicated). 
 By the way: You still can spin up the proxy and block / allow it there on the proxy, if you have a chance.

Yet Another FQDN Wildcard question :D

Top Replies