Web Server Security: Support for Wildcard Domain Routing
It would be great, if you could add " *.domain.com " in WAF.
So that you dont need to add every single FQDN for every site.
This feature will be included as part of UTM 9.2 which will enter beta in September 2013. Stay tuned!
Florian Albeck commented
Since we are nowadays at version 9.3 and there was no feedback to Kod4krome or this feature request marked as closed, I also want to ask:
Is this feature request now implemented and working or what is the common status on this?
Did this make it in?
Is this arealdy working by now in the latest release?
I tried to setup a dns host like '*.somedomain.com' or 'somedomain.com' or '.somedomain.com' But still not matching in the Firewall rule.
I would also like to vote for this feature!
I'd very much like to have this feature as well.
Just voted for this. Must be plain simple to implement.
Seconded! I have to account for all kinds of mis-spellings of our site name(s). It would be much easier to use a wildcard than to guess all of the ways folks on the internet will mis-spell things!
Elmar Haag commented
in the URL hardeing configuration, you can do this already. In the "virtual webserver" domains list not yet (9.002).