Hey Adobe - Why does embedded Flash-in-PDF content call flashservice.adobe.com?

Sorry for the delayed response.  I saw it come in, but I didn't want to reply until I could research it and provide a definitive answer.  I didn't want to guess and provide misleading information.

Based on the data you've provided:

1.) It's definitely not going to hurt anything to block this request.

2.) I think this is related to a long-dead feature, and this request was just grabbing a static config file from a trusted location on the server that allowed us to control in-client messaging without having to ship an update to the Flash Player binary itself.  It was a short-lived experiment, and the service and server are both long dead, which is why the DNS entry doesn't resolve. 

3.) If this is happening in current versions of the Flash Player plug-in for Acrobat, that's definitely a bug; however, I'm thinking that this is coming from stale clients.

I'm working from incomplete information, and a few things would help me definitively confirm that my analysis is correct, and what, if anything, needs to be done at this point:

• What's the full URL of the request?  (running a local web debugging proxy on the client would give you both the request and body)
• What version of Flash Player are you using in Acrobat (and/or is the request made in the latest version)?
  • Adobe Reader and Acrobat Flash Player Download for Windows
• What version of Acrobat are you suing?

Adobe, Please explain what is occurring when you reference flashplayer.adobe.com in a Flash embedded PDF files?  The only sites that we 'trust' are sites that we control.  If I add Adobe.com as a trusted site, what kinds of activity will be occuring (now and in the future)?  If I block adobe.com for all of my 50,000 users, will they continue to see the block warning notices?  How can I turn off the Block notices?