iHearU

I vote for this feature as well, expecially since your system has decided to block a primary domain that is a DynDNS provider, and I use sub-subdomains to manage access to different things For example: You have dyndnsprovider.com blocked (which in and of itself, I don't have a major issue with, as I do realize that bad actors use these types of services to phish) My subdomain: mysubdomain.dydnsprovider.com (as an example, has a current IP of 1.2.3.4) which is the only thing that actually gets set, which means all subdomains of this are effectively the same IP as my primary subdomain My subdomains off that: sub1.mysubdomain.dydnsprovider.com IP address gets resolved by the DynDNS providers DNS server as the same IP as my primary subdomain. sub2.mysubdomain.dydnsprovider.com IP address also gets resolved by the DynDNS providers DNS server as the same IP as my primary subdomain. Right now, in order to unblock it, I would have to set each subdomain as a standalone exclusion rule in Nebula, which is just absurd. There is no justifiable reason to not allow wildcards.