I have just got an interesting answer from MS about an issue I have: the first time I access a trunk , and it happens for each application on the trunk not just once, I get a significant delay. After the first load it works flawlessly until the config is activated again
The answer is with DNS - UAG analyses the site (actually it seems to analyse each page it sees for the first time) looking for URLs. It does a forward lookup for each URL it finds to know it's IP (in case HAT needs to rewrite the IP not the name) and a reverse lookup for each IP to ensure the name is correct.
So for every application, and every link in every application (eg the IIS demo page has a link to go.microsoft.com) the UAG box must be able to resolve the URL.
You can do this in your DNS or in the host file.
Once it does this lookup it stores the result and does not do it again.
