Include the abilty to use FQDN and/or wildcard FQDN for host isolation exceptions

I apologize if this is not the correct place but I imagine this feature request will involve the endpoint and changes in Kibana.

Currently the host isolation seems to be geared more towards segregating a device from a network in the event of a possible infection, but I believe this feature could be expanded upon easily to lock down device(s) permanently for specific use cases. My particular use case is a company distributing laptops to users so they can work at home but only wanting the user's to be able to access their corporations SSL VPN IP, Windows Update, and the corporations RMM solution. The issue is a lot of vendors provide fully qualified domain names for firewall whitelist and not individual IP addresses due to the IP's potentially changing all of the time. One good example is Windows Update (https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-troubleshooting#why-am-i-offered-an-older-updateupgrade).

It would be great if instead of just IP addresses for isolation exceptions we could put something like "*.update.microsoft.com" or "emdl.ws.microsoft.com" in as an exception.

** Side Notes **
Obviously in order for this to work the device would need to be able to make DNS queries. I think it would be up to the administrator to put exceptions in for specific DNS servers.