Every now and then my company will will do some intergration with a 3rd party, e.g. calling a webservice from our shared IIS webservers in e.g. some ASP page for instance.
Where these intergrations have to be IP white-listed at the other end, often the applications (or in my opinion the developers/sysadmins) are poor and will only accept a single IP to white list connection attempts from, rather than allowing our company's subnet access.
Since my webservers have multiple ips (different SSL certs etc) the primary IP of the server often has nothing to do with the site intergration in question.
As a result we now have various intergrations which can fall apart if the server were to be slightly reconfigured due to this arbitary sharing of primary IPs.
Is my request to allow entire subnets access for external services unreasonable?
Is there a way to work around the fact that servers calls services based on their primary IP rather than any other IP?