Re: IIS Website Question

Tech-Archive recommends: Fix windows errors by optimizing your registry

Use a hostname. The default website listens regardless of host name.

Make sure DNS is setup for [host].domain.local on your local DNS
server. This will resolve to the correct server's IP address. IIS
will receive the traffic on port 80, but for [host], not the default.

Anyone with DNS experience chime in antyime.

In a nutshell:

On your SBS server,
Start > Programs > Administrative Tools > DNS
Navigate to your local domain. domain.local
You'll see a list of hosts...all the workstations and servers on your
domain.
Right click on an empty spot; create new alias (CNAME).
Alias name = test (FQDN will be test.domain.local)
FQDN for target host = sbsserver.domain.local

Go to IIS Manager
Edit target website, or create new one.
IP address can be left on Default
Host header value = test (the same value you entered as the CNAME)

This should be enough detail for most admins to get it. If you don't
understand, you might need more help. Let us know by posting a reply.

Regards,
Alan


K.J. 44 wrote:
My default website is listening on ports 80 and 443. Is there a way to
redirect portal.mydomain.com from the default website but not
mail.mydomain.com?


ALeghart wrote:
Why not use different IP addresses, or use a host name? These can both
be handled in DNS. Port numbers cannot.

You can make a redirect to a host:port. Under Home Directory tab for
the IIS site "portal.domain.com":

The content from this resource should come from:
(*) A re-direction to a URL

Redirect to: http://server.domain.com:1234

The client will be sent to:
(*) The exact URL entered above


Be sure to specify HTTP or HTTPS as your needs require. The browser
should still show "http://portal.domain.com";.

If you want the URL to change to the new page, select the option:
(*) A permanent redirection for this resource

Try it to be sure links/pages/ports are working correctly. YMMV.


Regards,
Alan

K.J. 44 wrote:
Hi,

I have multiple websites on my IIS server listening on different ports.
On of them is only an internal website portal for people in the
corporate network.

Instead of having them go to server.domain.com:1234 can I set it so
that portal.domain.com automatically points to server.domain.com:1234,
this way preventing them from worry about the port number? (or even
portal.server.domain.com if I have to)

Thanks.

.

Relevant Pages

  • Re: Tracing emails from outside clients
    ... Wherever you wish to host the DNS just make sure you create the identical ... The secondary server arrangement is just a legacy thing. ...
    (microsoft.public.exchange.misc)
  • Re: Web Site Mystery
    ... host our own web site at this location. ... So in our DNS setup, there is a pointer to the ip address of the ... Run an ipconfig /all on your server and you'll see the ... www.europacrown.com don't work from our corporate network. ...
    (microsoft.public.windows.server.general)
  • Re: Web Site Mystery
    ... host our own web site at this location. ... So in our DNS setup, there is a pointer to the ip address of the ... Run an ipconfig /all on your server and you'll see ... www.europacrown.com don't work from our corporate network. ...
    (microsoft.public.windows.server.general)
  • Re: How to disable the "implicit mx record" in Exchange
    ... the host with the A record for the actual domain. ... So when Exchange gets a DNS timeout looking up an MX record, ... their own Exchange or other type of mail server under their own domain name, ... DNS UDP traffic max packet size is ...
    (microsoft.public.exchange.admin)
  • Re: How to disable the "implicit mx record" in Exchange
    ... the host with the A record for the actual domain. ... So when Exchange gets a DNS timeout looking up an MX record, ... our ISP's DNS and perhaps slow response from the recipient domain's ... their own Exchange or other type of mail server under their own domain name, ...
    (microsoft.public.exchange.admin)