This issue is resolved in VMware NSX 4.1.2.2.
This issue is resolved in VMware NSX 4.2.0
Additionally, you will need to add a rule after the upgrade to associate .example.com requests. You will still need a wild card for the site = *.example.com
Workaround:
You can add a rule in NSX DFW to accommodate the website access.
Example you use = Source *.example.com | Dest = Any | Service Any | Context Profile None | Applied to DFW.
You could adjust Dest, Source, Service, and Applied To depending on grouping who needs access to the website.
You may have VM's/Users not able to access a website.