I am trying to setup multiple applications within IIS, single server. I want all to use port 80 and the server has only one IP address.
I have created two application (site1 and site2) within IIS and modified the 'Host name' under bindings on each as follows:
site1.mywebsite.com
site2.mywebsite.com
and kept the IP address and port values to be 'All unassigned' and '80' respectively.
I have "mywebsite.com" through godaddy, and not sure how should I configure dns zone file to take this into effect. Please help....
(My ultimate objective is to have n+1 sites hosted in the same server, so that site1.mysite.com through siten.mysite.com points to their respective application, and every other subdomain points to n+1 th application.
Is this a possibility?)
Thanks in advance,
Anuruddha
Both site1.mywebsite.com and site2.mywebsite.com must point to the same IP - one assigned to your server by GoDaddy. So as long as users access the sites by host names you're fine.
Related
Right now, i have my default website in my server. Here is the binding details
Port : 80
HostName : (Blank)
IP Address: *
And then my custom Application
Port : 80
Hostname : myPortal.com
IP Address : *
If I browse my application with myPortal.com, its coming up fine and I dont have any issues. Here is the Problem. For application availability purpose, i have four failover servers and the application is configured in the same way for each server.
If I want to browse my application with server name in order to find when one of the server is having issues, i m not able to do it
say for eg, if i browse, myPortal.com, its working but if i want to browse myserverA.com, its going to default website
Approach 1 which i tried:
To Overcome this issue, i made host name field as blank for my custom application and updated it with localhost for IIS Default website.
Doubt 1:
It served my purpose but i scare if i have to host one more application in the server default port, i will be getting into trouble. Are there any best approach to solve this issue
Approach 2 which i tried
I left the host name as blank for Default Web site and had myPortal.com for my custom Application and then edited the IP address field for my custom Application. I changed the IP address from "All Unassigned" to "Server IP address"
Doubt 2:
It served by purpose of browsing my application with myPortal.com and myServer.com but what is the impact of changing the IP from "All unassinged" to "Specific Address"?
Also, in future, if i host one more application in default port with different host name, how would i be accessing that server with server name or IP name?
That's exactly what's desired.
To access a certain site with host name on a specific server, you can go and modify hosts file, add an entry for the host name and point to the IP of he target server. Then in your browser you can access it correctly.
Here is the solution which finally worked out
In the custom application, under EditBindings, add one more binding
Leave the hostname as blank for the new binding. Add a port number other than 8080
It helped to solve below issues
I m able to access my custom application through myportal.com and
Also in scenarios, when i have issue with one of the shared servers,
i can try accessing each of the server site individually through
serverNameA:port
So in future, if i want to host one more application in the default port, i have to register new host name for that server and will add one more additional binding for browsing with server name
How can I access different websites hosted on my local IIS 7.5 (using different bindings) from my ipv4 address?
My system32\drivers\etc\host file has my binding names mapped to 127.0.0.1
In IIS, I have the normal "Default Web Site". Its binding hostname is empty, set to all unassigned ip address and port 80. On my network, I can access this site using the server ipv4 address like so : http://192.168.2.1/mySubSite/index.html where mySubSite is a child folder of the "Default Web Site". I can also access it locally using http://localhost/mySubSite/index.html
If I setup a second website in IIS using the same binding as the "Default Web Site" but using a hostname (say "site2"), I can access it locally using http://site2/mySubSite/index.html.
How can I access this second site on my network the same way I access the "Default Web Site" using the ip address? Is it possible?
the easiest way to do this is to change the port binding on each website. This takes minimal configuration and you can place a website on any port you want (I recommend ports over 1024...to a maximum of 65000)
For example, your default site will automatically be on port 80. Place site 2 on Port 2000. Then you can access your default site like you have above, and you can access site 2 with a similar url like http://192.168.2.1:2000/mySubSite/index.html. Notice the port is specified in the url using the :[port] at the end.
Yes, you can have multiple sites on the same IP address and port. It is called binding by domain name.
Open ISS and go to your first default site (one that is functional) and then go to edit bindings. You will see by default it states "http: Port 80 IP Address *"
Notice the hostname is blank? This is where you can tie a domain name to that exact port. Fill out domain name on both your site bindings. This means when someone comes in from that exact domain name, it knows where to forward traffic too. If port 80 inbound doesn't match either of those two domain names, it will default to w/e site has no bindings such as the "default site".
We are a few web developers and currently edit our host file to point domain names to the local web server but this is becoming hard as number of clients are increasing and we need to continuously change each host file of computers.
What do you think is the best possible solution for us, use a proxy server or a dns server, and could you possibly tell me how to fix this problem?
Thanks in advance
I would use a DNS server, or use mDNS, on your LAN. Then an administrator can simply add an A or CNAME entry to the zone, and all the computers on the LAN will see that record.
I developed an asp.net (2.0) intranet Application for local network in an organisation..
so we have 10 systems every one should access that site by ://192.xxx.x.xx/xyz(website name) ...
so now their requirement is not to type total ip adress.they need just by typing ://xyz they have to browse the intranet application..how to solve this issue..?
Thanks
Veduru
Go to every one of this 10 computers, and in this directory
c:\WINDOWS\system32\drivers\etc\
find the host file and add the conversion of ip to name as
192.168.1.10 xyz
etc
and then you can access the site as http://xyz
Talk to your network admin about setting up a DNS entry for your application in the local DNS server. If you have multiple web sites running on your web server, look into configuring IIS host headers to ensure the users get directed to the proper web application.
Please do not manually edit the hosts file on each machine unless it is absolutely, positively necessary, and only do so as a last resort. When your 10-machine application expands to 100, or if your server IP ever changes, you will thank me later :)
I am using SharePoint Server 2007 Enterprise with Windows Server 2008 Enterprise. And I am using publishing portal template. I have a physical server with a single IP address, and I have set in DNS to map two domain names (server1.mycorp.com and server2.mycorp.com) to the same server/IP address.
My question is how to setup two SharePoint web sites on the same server with a single IP address to serve two domain names individually (with the same port number 80)? My current idea is to create two SharePoint web applications for the two web sites, with the same port number 80, but with different host header (setup Http host header to server1.mycorp.com and server2.mycorp.com individually for the two SharePoint web applications). Not sure whether my idea is feasible?
thanks in advance,
George
I believe this belongs in ServerFault.
And you also seem to describe a common host header concept, when you create your WebApplication in the SharePoint Central Admin, you will define a host header, being on the same IP or not, IIS will respond to them individually, so yes it works.
Application Management => Create Web Application => define host header, define same port 80, done.