TechNote (Archived)

How does Breeze resolve DNS names? (Windows)

Issue

Breeze Meeting may not work properly until a host entry is added in the header parameter.

Reason

The HOST_HEADER info may be changed by a proxy server and must be allowed to resolve through a firewall.

Using Breeze Presenter or Breeze Meeting relies on the header parameter HOST_HEADER (found in every request). This value, which is in the request stream, must match the ADMIN_HOST value in the custom.ini for Breeze 4.1 or older. In the case of Breeze 5.0 or later, the value can be found in the Application Management Console. It is in the ˜Host Mappings: under the ˜Server Settings tab. Most of the time, this is an external DNS name, such as breeze.macromedia.com.

In order for Breeze Meeting to resolve, Breeze Meeting has to be able to send a request to a FQDN that matches the setting in ˜ADMIN_HOST or the value found in the ˜Host Mappings:, for example, breeze.macromedia.com. Sending this request may go through a firewall or even a proxy server. If the firewall doesn't allow this or the proxy server changes the value of the HOST_HEADER when it returns to Breeze Meeting, then Breeze Meeting will fail. Breeze Meeting must be able to resolve the URL.

Solution

If Breeze Meeting fails and you suspect either the firewall or a proxy server is the problem, then add an entry in the Breeze servers hosts file. This way, Breeze Meeting will resolve locally and will not need to pass through the firewall or a proxy server.

Note: Keep in mind that with more complicated setups, where Breeze Meeting is on a different server, it will have its own external DNS, which must resolve as well.