Yeah - I was afraid the FQDN was not going to resolve on the fly. I thought they had a refresh mechanism for this now, but it may not have been actual address objects I was thinking of. I could require all clients to setup a forward proxy, but I'm trying to make this transparent to the end users (not all of the clients are under AD control). Plus I'd have to deal with all the traffic going to the proxy, which I don't want, just youtube. I'm liking the idea of a dns-resolver pointing to the proxy. Why would there be a caveat of worrying about setting YouTube IPs in the proxy? Only traffic looking for *.youtube.com would hit the proxy, and the proxy should be able to handle the lookups normally to provide the content. Or am I not understanding it correctly? Would I be able to accomplish this on the PA itself, or just through setting my internal DNS servers to resolve the youtube.com domain? Thanks!
... View more