WCF Really Doesn't Support Multiple Host-Header Applications On A Site...?

I had a situation where due to firewall NATting I had to assign a new IP address to an IIS web site, and a host header was assigned to the site as well. It appears that WCF doesn't support complexity like that; I got the following error in the Event Log:

This collection already contains an address with scheme http.  There can be at most one address per scheme in this collection.

Clear as mud.  More info (and bitter complaining) was found here:

http://social.msdn.microsoft.com/forums/en-US/wcf/thread/9e248455-1c4d-4c5c-851c-79d9c1631e21/

Yeesh.  My solution was to create a new IIS web site, use only the new IP address on that site (removing it from the old one), specify that the host header should be used on the new site, apply the existing SSL certificate (this was an HTTPS web service), uninstall the web service, and reinstall it on the new IIS web site.  

I was greatly afraid this would require some kind of config file change or--worse yet--some kind of code change.  But fortunately, no.