I have a couple of configuration questions:
How do I configure the local web site to use IIS. I need to run the web site using IIS server not default visual studio web development server.
How do I give the solution name for website.
For example, normally when you create a web site it will display the website name as:
http://localhost/testproject or d://....../testproject
But I need to display the web site project name as testproject alone
Modify your hosts file to point at your ip address with a dns name for the second bit. Then set up your dns name in a website in iis. When you browse to the dns you will hit your website iis will strip the dns name for it and forward your request to the correct site.
For the first bit its too long winded you will have to read a tutorial..
Related
I have installed a web site on one of my servers within our active directory domain. How do I create an actual URL such as http://TheWebApp instead of having users navigate to http://192.168.0.xxx/TheWebApp?
Thanks,
Chris
You can add 192.168.0.xx and WebApp to hosts file in local machine. Then set the application as an independent site on server and bind to localhost:80. When you enter the http://WebApp in local machine, it will forwards to http://192.168.0.xx and points to the site on server.
Or you can buy a public domain and bind it to your server, then bind site to domain.
I have an Azure web app up and running, using a custom domain purchased outside of Azure... and that all runs fine. So I have https://myappname.azurewebsites.net/ loading fine with my domain name URL https://www.myappname.com
I'm trying to upgrade the web app, though using Azure Traffic Manager. I've cloned the app a few times, each on its own app service plan, and I have the traffic manager all up and running fine. I can successfully hit different versions of my cloned website based on the traffic manager configuration profile... so no issues there.
The only issue is that I can only access the "traffic managed" version of my website via the standard azure URL -> myappname.trafficmanager.net.
All examples I've seen say all I really need to do now, is go into my DNS Management screen, and add domain forwarding, however, my online DNS management tool does not offer this option.
I can't really change my A record in the DNS management screen, because I don't know the IP address of myappname.trafficmanager.net
Every place I've tried to change the name of the current/working Azure URL (like in awverify text files, www cnames, etc.) does nothing. The DNS still points to the single instance which remains in the IP address od the DNS managers A record.
Also, since my live/single instance is linked to the domain name (along with the SSL binding), I can't add those properties to the clones, which makes sense....only one version can be live. However I could unbind that when I make the switch from the single instance web app to the traffic managed set of clones, but I fear I can only bind that to one of the clones. I can't seem to bind it to the myappname.trafficmanager.net version, which might cascade down to all of its endpoints. Is there a way to bind my domain name and SSL cert to more than one version of my web app?
Thanks!
Is there a way to bind my domain name and SSL cert to more than one
version of my web app?
I don't think you can do that unless you have two different domains or subdomains with each own SSL cert. Each web app hostname is unique globally and each SSL binding is attached with the web app domain name.
If you have a purchased domain and just keep the default xxx.azurewebsites.net as each hostname. Then you could configure the two Azure app serves as the endpoint of TM.
By default, Azure provided a wildcard cert for this domain *azurewebsites.net, so you can automatically access this hostname with HTTPS without any extra cert. Then use a CNAME record www in the domain domain.com in your DNS provider to point to the traffic manager hostname myappname.trafficmanager.net. Since Traffic Manager works as DNS level, it does not validate the server and client SSL, you could safely ignore the SSL warning when accessing with traffic manager hostname.
Feel free to let me know if you have any question.
We have PHP based site host on (XAMPP) locally configured which we can access this site by typing dashboard.xxx.com. we have made entry in local DNS against this dashboard.xxx.com.
I have setpup sharepoint site on office365 which can be access through
https://crescentpk.sharepoint.com/sites/portal
I want to replaced my local server with above sharepoint site but I do not want to change URL.
If you're strictly interested in having the "dashboard.xxx.com" forwarding respond on the network served by your internal DNS, then here's a couple options:
Leverage the existing PHP site infrastructure to use Mod_rewrite (https://httpd.apache.org/docs/2.4/rewrite/remapping.html). Forwards all requests for dashboard.xxx.com to https://crescentpk.sharepoint.com/sites/portal
Modify your local DNS records to forward the cname dashboard.xxx.com to your SP site collection URL.
If you're looking to meet your URL requirements on the global intranet, unfortunately there's no means to direct your cname to a specific Office 365 private Site Collection, since the server path portion of the URL is not controlled by DNS, and there is no URL rewriting at that level provided by Office 365.
I got an AMI of Windows Server 2012 running on Amazon, and use it as website container for all my web sites. I recently created an app in WinForms, I need to publish it. In the moment that I use the publish option it asks for an FTP site. I already use FileZilla Server. I created an user and account. The matter here is that it asks for an FTP URL (ftp.example.com) and I only got (http://example.com). I try to do this with IIS but only can do it with HTTP. How can I create an FTP URL for the site that will contains my ClickOnce app ?.
Check Public DNS column on Instances page of Amazon EC2 console.
Note that the public DNS may change when the instance is restarted.
So your FTP URL would be like:
ftp://ec2-45-123-87-128.us-west-2.compute.amazonaws.com/
Though, you need to configure the instance firewall to allow the FTP traffic, what is not easy in general. But that's out of scope of your question.
I have a Default Web Site and another web application (let's call it Application2) inside the Default Web Site in IIS7.
I have 2 registered domain names, let's say www.example.com and www.example.net.
I would like to configure things that when I open www.example.com I get Default Web Site, when I open www.example.net I get Default Web Site/Application2.
www.example.com -> Default Web Site
www.example.net -> Default Web Site/Application2
How can I do that?
First you need to decide if your going to use Name Based or IP Based hosting.
IP-Based uses unique ip's to determine which virtual host it will serve and Name Based will actually use the host header which is sent by your client browser.
So let's see two scenarios:
Scenario # 1 (ONE IP TO SHARE)
You have a server with only one IP, could be either private or public as long as the domains you are serving are properly configured in the dns serving you internally or your client externally (NAT).
I suggest that for the sake of this tutorial you stop the default website. Ok.
You will set up one site in II7 and name it accordingly. Go to the right hand side of the manager and look for "Bindings" under actions menu; making sure you have the new site selected on your left pane. Now under "Site Bindings" select the ip address you will be sharing between the sites (name based hosting). Under "Hostname" enter domain # 1 "www.example.com", hit ok.
Follow the same procedure above with the other domain or domains, making sure they have diferent hostnames and same ip's.
That's it. You will now be able to start those sites and run them at the same time.
The same principle above applies if your using the "Default Site". "Default Site" is just a name MS gave the default created one.
Scenario # 2 (MULTIPLE IP TO SHARE)
If you have either some private or public ip to spare, or at least until you do the exercise the only diference here is that sites you will set up and don't have to specify the "Hostname" per each site, as this is basically done in the DNS zones itself. The sites will respond for any request made to those ip's on port 80 regardless.
When will you need to use multiple Ip's to serve websites. Well it all depends.
Some reasons are: Network Isolation (Security), Applications which don't work well under name based hosting, SSL Certificates Bindings 443(PRE II7), and mostly complete control over site. There are of course more reasons, but I'll let others write a bit also.
Have fun.
Edit... upon further investigation I found that if you can set up multiple sites and run them simultaneously. Just need to stop and start the sites after setting the host values to get them to both run at the same time.
Original post:
The straight-forward way to do this would be to add another application by opening IIS and right-clicking Sites then select Add Web Site. In there you can specify the physical path of Application2 and also set the "host" to "www.example.net" which will filter all those requests to your second site. Any requests that don't match "www.example.net" will still go to the default web site.
That approach will work fine on Windows Server using IIS, but on Vista's IIS7 it won't work since you can only have one site running at a time. To start the second site, you'd first have to stop Default Web Site.