Im tying to get my head around the temp url function...

we have an anonymous domain running on one of our linux servers here at TP which we use to run all our servers from for anonymours nameservers etc...

we have a helm server runnign from this domain

lets call it helm1.server.com

and it uses ns13.server.com and ns14.server.com for its nameservers...

all works fine apaprt from the temp url

we want to add helm1.server.com as the temp url so that people on the server can use it to access their domains but it wont let us...

how can we get this to work?

Ive been told by a couple of people the domain itself needs to be hosted on the helm server, which i find a bit weird??? and is impossible to do in this instance...

any suggestions?

Helm needs to have control of the DNS server that's hosting the tempURL domain as well as the IIS server that's hosting the domain receiving the tempURL. It adds a host record for the tempURL into DNS and then adds the respective host header onto the site in IIS.

If your DNS for this temp domain is hosted on a Linux server, then it won't be possible for you to use this feature. However, if your Helm installation is using a single server, you may be able get away with it by pointing a wildcard entry for the domain at that server's address.

Kyle

thanks for the tip

I think i follow the wildcard idea...
will give it a try

what would occur if we had more than one helm server deployed? (we run everythign except MSQL on each server)

By using a wildcard, you're effectively saying "point everything for *.domain.com at xxx.xxx.xxx.xxx." If you have a single server setup, you know that the site you're pointing the tempURL to will be on that server. With a multi-server setup, you have no guarentee which server the site is located on.

It might work if you used different domains as a tempURL base for each server, but I don't even think Helm supports that.