CSS doesn't work with IIS host names multi-subdomain

[lanningye]

Hi,

We  have two servers behind CSS. Once we enable more than one host name on IIS for multi subdmain. e.g. a.test.com and b.test.com

we http to this address will be time-out. all the domain names use single IP address.

The configuration on CSS is very basic and simple. and to keep it even simpler, I have only added one service to the content for now

!*************************** GLOBAL ***************************
   ip route 0.0.0.0 0.0.0.0 xxx.xxx.140.1 1

!************************* INTERFACE *************************
interface e1
  bridge vlan 2

interface e5
  bridge vlan 3

interface e6
  bridge vlan 3

!************************** CIRCUIT **************************
circuit VLAN2

  ip address xxx.xxx.xxx.3 255.255.255.192

circuit VLAN3

  ip address xxx.xxx.10.1 255.255.255.0

!************************** SERVICE **************************
service Server1
  ip address xxx.xxx.10.3
  keepalive type http
  active

service Server2
  ip address xxx.xxx.10.4
  keepalive type http
  active

!*************************** OWNER ***************************
owner test

  content test

    add service Server1
    vip address xxx.xxx.140.4
    protocol tcp
    port 80
    active

Does anyone know what configuration I missed here?

[pablo.nxh · Accepted solution]

Hey there,

I'm thinking your problem is related to the keepalive. Here is what happens:

Currently you've got configured keepalive type HTTP under the two services but not URL string meaning that the CSS will

do a HTTP head looking for the default website you enabled on your IIS server. Now when you enable HTTP host headers your default

website is gone, each website has its own URL and only traffic specifically destined to that URL will be sent to the domain in question.

When host headers are turned on the keepalive on the services dies and they will be brought down.

Please enable host headers and run the command show service summary and look for the status of the services!

If my assumption is correct you have two options, either set the keepalive to be TCP port 80 or you can use the scripted keepalive to check

host headers separately.

HTH

__ __

Pablo

[lanningye]

Thanks Pablo! That got straight into the solution!

Thanks for your response!

[pablo.nxh]

Sweeeeet! Glad to help! =)