I have been looking for the answer to this but unable to find it thus far.
I have an Azure Windows VM with 3 Websites on it. I have managed to configure one domain to point at the IP Address of the Server (A Record) but when I try to point domains to the other two sites, I cannot specify the port number.
How would I go about getting additional custom domains to point at different ports on my VM?
Thanks! Tom
You cannot map different domains to ports.
What you can do, is map domains to specific sites on IIS and have them listen to that specific hostname. Godaddy has a guide on how to do that here
Related
i have a server that has a common dns and hosts multiple containers of different applications but the problem here for each domain name for an application, any app on the server can be accessed with the right port number. i have an internship management system and hospital management system on a single server with the respective domains; ims.ius.ca.com and hms.ius.ca.com where the common dns is "ius.ca.com". These two application have different port numbers 2301 and 2401 respectively. However, when a user keys hms.ius.ca.com:2301 the internship management system application is accessed instead of the hospital management. How do I resolve this conflict.
I agree with #Martheen The common solution for this problem is to have a reverse proxy in front of your applications (docker applications). You could use Nginx or HAProxy as reverse proxy.
I "own" a URL www.example.com which is currently hosted by One.com. I recently built my own server running a LAMP stack and it serves pages to the internet from /html as it should, but is only accessible via numeric IP address. In the past I've re-assigned the name servers for URL's but only using a hosting company's "dashboard" or GUI. I've read about changing the DNS settings in Ubuntu (my server is running 18.04) and also I've researched what I can into Google's public DNS and DynDNS services.
So I have two sets of questions. First, is it possible to "connect" or "bind" a URL to the static IP address of my own server without using a DNS service? Can it be done through any kind of public registry and if not, what are the least expensive but still reliable options?
Second, is basically "Why bother?" I do understand the value of a human-readable address but also, the address bar isn't realistically used anymore. Most of the security value of having human readable addresses depends on users actually looking at the address bar so that's becoming a moot argument. People only navigate the web now through links and Google searches, and the address bar is essentially a developer tool. It seems like I can pretty much replace the need for DNS with masked links and meta titles?
You need to set your domain's "A Record" in DNS to point to your server's IP address. While not neccessary, you can configure Apache to respond to the correct domain with virtualhosts [https://httpd.apache.org/docs/2.4/vhosts/name-based.html ], but you will need the DNS configured correctly first.
It is not possible to bind a domain to an IP address without DNS - DNS or Domain Name System is THE authoritative system for doing so. It's how the world wide web functions.
Here is some additional reading on what DNS does and why it's important: https://www.cloudflare.com/learning/dns/what-is-dns/
I have two websites hosted on the same server via IIS. The two websites thus have the same IP address and use the different ports. And this is how we differentiate the two.
We are in the process of DNS mapping the two URLs, but the team that handles this, says that it cannot incorporate the port number in the URLs.
Is there way from IIS to identify the particular website from the URL itself and direct it to the same?
UPDATE: I tried adding new IP address, but the newly added address doesn't show up in IIS site bindings.
You can bind multiple sites with same IP address & Port.
But you need to configure host header in site binding.
Refer this link.
http://blogs.msdn.com/b/varunm/archive/2013/06/18/bind-multiple-sites-on-same-ip-address-and-port-in-ssl.aspx
hope this will help
I would like to know how to access websites by IP address in a server that hosts more than one web application?
Currently I can get the IP address of the server, but it points to one site by default. Is there a prefix or suffix that I can add to the IP address to get a particular website in the server?
Eg: I would like to access by IP address:
http://mysubdomain1.domain.com
http://mysubdomain2.domain.com
http://mysubdomain3.domain.com
The server hosts many ruby on rails web apps via nginx and unicorn.
Thanks in advance.
Assuming that the server has one public ip address, and been set up to serve virtual hosts, you can do that like this:
curl -H "Host: subdomain.domain.com" IPADDRESS
I don't think your question has enough information to be answered accurately not in depth.
Here are some thoughts.
There are different ways in which websites can be hosted. Via IP, aliases, named virtual hosts, etc.
There's a good chance that the server that's hosting those websites uses named based virtual hosts https://www.digitalocean.com/community/articles/how-to-set-up-nginx-virtual-hosts-server-blocks-on-ubuntu-12-04-lts--3
That is, one ip points to multiple servers. In that case, the only way you can get to it, is by knowing the domain name.
Here's more or less how it would work
User requests http://mysubdomain1.domain.com
Server with single ip has an entry for that subdomain1 and forwards requests to it.
I have a scenario where I have many domains (could be hundreds) pointing to my one web application for example
site1.com
site2.com
site3.com
.... etc
All point to my single web app, this app will be in a shared hosting environment.
The only way I can think of configuring these bindings in IIS is to send my shared hosting company an email every time I need a new binding. Is there a better way? for example some how sending all host headers to my site? How do I do that?
You probably need your own IP address to do this. Then you could just not specify a Host name in your binding:
You will need to specify your IP in the binding though.
This means that as long as your DNS points all sites to your IP, then your site should respond.