The option to create a DNS host object in the Access Control portion of Site Path Routing for a Virtual server doesn't appear to work anymore.
When troubleshooting this issue, if I create a static Host object and add it to the Allowed access control field within the site path routing it works as expected. However if I have a Dynamic DNS based DNS host object that UTM has successfully and accurately resolved to that same static address, I am greeted with a 403 forbidden message after removing the static host object from the list.
This used to work in previous versions.
This thread was automatically locked due to age.
