Yeah, seems to be ok without having to reload.
Have just been testing and wondering about certain domains that have continuously changing addresses. What causes the cache list to be updated.
Let's say a user gets a response from the corporate dns with an address no yet cached on the Aruba. The user tries to go to that address. When it hits the acl, will the Aruba do a lookup to see if that address matches the netdestination or will it just move to the next rule because it is not yet cached?
I'll do a little testing in the meantime.
Thanks