IIS host header without an external DNS entry or seperate port

On an external web server i see we a default web site on port 80 and
few other sites that come in from an external DNS entry.

I need create a new external site that will only have a single page
that will be visible fromt the outside and actually will only be
called from an Iframe of another external site.

Is there any way to accomplish this without a new external DNS entry?


Also, I attempted placing the site under the default website as a
virtual directory, but that only results in "Server Application
Unavailable" I think because the sites root has a full blown
web.config.

Thanks for any help or information.

Re: IIS host header without an external DNS entry or seperate port

As long as the client sends a corresponding HTTP Host: header, then there is
no need to use a DNS entry. However, the question then becomes, how are you
going to get the client to send the Host header? If you write the client, or
the client machine has an entry in the HOSTS file, then you are set.
Otherwise, I think you may have a problem.

In terms of the second issue - did you try making the folder an application
root?

Cheers
Ken

wrote in message
news:89d52d58-64a5-4680-be1c-e97b7184e8b4@a1g2000hsb.googleg roups.com...
> On an external web server i see we a default web site on port 80 and
> few other sites that come in from an external DNS entry.
>
> I need create a new external site that will only have a single page
> that will be visible fromt the outside and actually will only be
> called from an Iframe of another external site.
>
> Is there any way to accomplish this without a new external DNS entry?
>
>
> Also, I attempted placing the site under the default website as a
> virtual directory, but that only results in "Server Application
> Unavailable" I think because the sites root has a full blown
> web.config.
>
> Thanks for any help or information.
>