I have an IIS server on which am trying to run two copies of the same website. I have only one public IP for this server.
So, to differentiate which site to open, I created two masked host names like
site1.mysite.com
site2.mysite.com
Both these masks hit the same public IP on the same Port 80.
Now, in the bindings, I set the two websites to be mapped to these masked site host names.
And when I hit the sites, I get 404.
if I dont use a mask, by doing a http://localhost - am able to open the site correctly.
Any thoughts on what could be wrong ?
First of all, please check whether the request has been logged in IIS. If the request is not logged, then there must be something wrong with your IIS binding or DNS entry.
So the problem is how did you register the masked host name?
1.Please ensure the website can be accessed from your public IP address. localhost always mapped to 127.0.0.1. So it doesn't represent public ip can be accessed. If it is not accessiable from public IP. Please ensure your server is mapeed to DMZ.
2.Now that you are trying to access website from public IP, please ensure you have purchased the domain name and map it to your public domain. If you are registering the site in hosts file, please try nslookup and check whether it is mapping to the right place.
3.Please try to stop other sites and only start specific testing site. Then set your binding with host name and IP address.
Related
I have a very simple scenario that I can´t make it work.
I created a virtual machine, installed iis, already can see landing page of IIS if I enter public IP on my browser, so it is well configured on firewalls and whatsoever...
Just for making this example more accurate, I changed port of that webpage to 8888, and also keeps working on my browser if I enter 1.1.1.1:8888... cool.
Now I want to associate my "contoso.com" address to this IP and specific port of my IIS.
Anybody knows how to do that??? Cause all I can find are lots of solutions talking about how to configure DNS to WEBPAGES.AZUREWEBSITES.NET, and I don´t have one of that... I have MYVM.CLOUDAPP.NET.
Thanks for the help!
All you have to do is to add a HOST (A) record in your public dns provider to point to your Azure VM Public IP Address. The port doesn't matter.
I am able to access my website via the domain name outside of the network.
On the internal network I am able to access the site via "localhost/websiteName/", "internalIP/websiteName", and "computerName/websiteName", but I am unable to hit either "http://example.com" or "http://www.example.com".
I was able to get it to work on a computer by adding the ip and website to the hosts file, but I am still unable to access the website using the domain via mobile devices on the internal WiFi.
I completely disabled the firewall, so I know that that is not the problem.
I have bindings set up for www and without www with all IP Adresses unassigned.
I did try adding a binding for both www and not, using the internal and external IP addresses, both IPv4 and IPv6.
I am running this on http without any certificates.
I have a cname record for www
My # record is pointing to my external, static IP
The website is set up separately from the default website and it is not a virtual directory.
I am using Comcast Business with their Cisco DPC3939B router.
This is initial setup of the website, and it is not an issue that just started after having worked previously.
I figured it out. All I did was add an # record to the DNS to resolve the website to the internal IP. Here is a really great reference for accessing websites on a Local Network: devside.net
i need to point from my hosting account to my local server
so i thought the best way is to do it using a subdomain
though the issue is that i cant figure which is the right way to do it
using same DNS as my domain / leaving it blank
using my internet isp dns maybe ?
what is the right way to point a subdomain to a static ip of my isp internet account at home ?
You don't need a subdomain, you need an A record (address). You could set up a subdomain, and then use an A record within that, so, if your domain is example.com:
Your domain is set up as example.com, your public web server A record might be www.example.com. You could then set up your home server A record as homeserver.example.com
A sub domain might be 'home.example.com`, and a server in the sub domain will have an A record of myserver.home.example.com.
In all these cases the IP address of your A record should be the IP address of the network side (external side) of your home internet router. If the address is static this will work, but if it's not you'll need to subscribe to a DNS service that supports Dynamic DNS, and that's a whole different story.
How you go about setting all this up is ISP-dependent.
Note that the external address of your network will not match the internal address of your server, so you'll need to set up port-mapping on the router to allow inbound traffic to reach your server.
..and lastly, do you really want to risk opening up your home network to the ravages of the public internet? Do this only if you really know what you're doing, and possibly not even then.
I am having an issue getting an IIS 7.5 website to answer when I connect to it using an IP address.
I have a Win2008 Server set up with IIS 7.5. It has only one IP address bound to it (10.10.10.10), and IIS listens on it just fine. I have IIS hosting two websites: defaultsite and mysite. Both of these two are necessary to be present. (To be fair, I have many more sites, but 2 will simplify things.)
Defaultsite is your typical IIS default site and has an IIS binding of "*:80:"
I want to access "mysite" via the DNS name but also the public IP address 1.1.1.1. So I've added the appropriate bindings:
":80:1.1.1.1"
":80:mysite.com"
My DNS and load balancer are moving traffic just fine to the IIS server. Everything works fine when hitting the server via "mysite.com" and I get the defaultsite if I try other ways to get to the server.
The problem is when I use 1.1.1.1 to get to the server, I get there, but I'm still sent over to the "defaultsite" rather than "mysite." My IIS logs and the file contents I retrieve verify this behavior.
Any ideas on how to get an IP address set as the host header on a site binding? (Searching for this situation is vexing; since all my key terms are present any time you work with host headers/bindings.)
Remove the binding for *.80 from the default site and make it respond to 10.10.10.10 and then your other site will get picked up when you type the 1.1.1.1 site. IIS is responding to the request but the rule states 'If any site comes through on port 80, respond to the default site'. The DNS name works because you are going by name and the lookup is not there on the default site.
We are installing a security camera system in our company which comes with a DVR that hosts a website on which you can view the cameras via the web.
I have setup the DVR with a static IP of 192.168.120.199 on our network and can view the website while on our network (either when at work or logged in via VPN). The camera DVR uses port 80 for viewing the webpage and port 9000 for Media Port.
We use GoDaddy to host our DNS info and I have added an Host(A) record of 'cameras' that points to the address of our server. I have also added a forward lookup Host(A) to our domain's DNS manager of 'cameras' that points to 192.168.120.199. When I use the address 'cameras.mysite.com' within our domain the website displays properly, but when I try the same address from outside our domain (ie, at home) it displays the default IIS 7 page (from our domain server).
Two questions about this setup:
Why does the forward lookup work when inside our domain but not outside (why does it go to the IIS default page when outside the network)?
How do I get this to forward correctly if not via the forward lookup host?
Because internally you're looking it up on your internal DNS server and you get the right 192.168.x.x machine. When you look it up externally GoDaddy is giving you back the 192.168.x.x, but that's not a publicly routable IP, so doesn't go anywhere. If you really want to be able to connect to your security cameras from outside your facility then I suggest setting up a VPN for security reasons. But if you want GoDaddy to directly route to your internal machine from the public internet then you'll have to give it a publicly routable IP.
As a further note on that - 10.x.x.x, 192.168.x.x and 172.16-31.255.255 are not publicly routable. They're called private IP blocks.