Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have a small problem, looked here & other forums, but could not find solution.
I have site at my-domain.com, site is on shared host. In my domain register I added DNS servers which hosting provider gave to me when I opened hosting account for my-domain.com and all that works for 1 year. Since traffic to site increased, hosting company told me to move my site to vps or dedicated server on their hosts or some other hosts, so I found good offer on another provider and bught 1 vps with tech specs that I need with ubuntu 10.10.
On the other side, I makde on my computer ubunutu 10.10 installation and rewrited application for better performance (web server/mail server/database etc...) When I make backup on my home machine, and upload and extract on remote VPS everything is as it should be, but I ma testing using VPS IP address, site that users and search engines access is on old shared hosting still.
Now I want to add new remote vps IP to my domain register NAME servers, but I don't know:
-should I add my VPS ip?
-in that case what be my secondary name server?
-what I need to do on my remote VPS with complete site(app) to edit so it can be accessible to my-domain.com?is that hostname, or what?
I hope that You understand what is problem, and I am sure that this is something simple for people who are doing with those stuffs,so please help me.Thanks
Just to explain, you have multiple things here:
Domain name
DNS nameservers
Web server(s)
All of these can be hosted with separate providers, but depending on your provider you might have different management options.
Domain name
Your domain name has a registrar (who you bought it from). That registrar will keep a list of 1-3 'nameservers' which are the addresses for the provider that hosts your DNS.
DNS nameservers
Your DNS is like your address book. That needs to be hosted somewhere, and if your old host didn't let you edit it, it's probably just part of their shared hosting service, and not something you can manage. You will need to change your domain name to point to another set of nameservers at a provider you can manage. Your VPS provider probably has a DNS service, but possibly not free (although many are). If needed you can use a free DNS host like XName or ClouDNS, but depending on your level of knowledge you might find these difficult to use.
A basic web server record you will want to add is known as an A record, and will point my-domain.com. and/or www.my-domain.com. (using a separate record) to your web server's IP address.
Web server
Your server has an IP address. If you need to load-balance for performance reasons you'll need your hosting company to provide you a 'virtual IP' or a load-balancer service, behind which you can have multiple servers.
Summary
The way the request goes is:
User types my-domain.com into their browser
The user's ISP's DNS server is queried for my-domain.com
The web server IP address for my-domain.com is returned
The user's browser sends a HTTP GET request to your server to get the web page
One part of the process leads onto the next, so you need to make the 3 things work in harmony to get your site to function.
Related
I am a bit new to the deployment of a website. I have a server which is written in Node.js. Previously I had been using Heroku for deploying my apps without knowing much about deployment. I would like to know how do I deploy my server to create a website which has .com at the end of it like www.example.com and not www.example.herokuapp.com. I think it has something to do with domains (correct me if I am wrong). I would like to know what exactly is a domain and a DNS provider and how to deploy a website in such a way. Thank you.
You should ask one question to yourself when you hit www.example.com in browser how does it load a page?. When you run a website on your laptop it basically runs locally, if you want to access your website over the internet you would require public IP(host or server) accessible over the internet so you can access a webpage using public IP:port. But this is not the best option because IP may change in the future and also remembering IP for each application will be difficult. Imagine if you access Facebook, Instagram or any other websites by its IP addresses how difficult and inconvenient would it be? There are a couple of things you should know.
DNS-> Domain Name system
Every host is identified by the IP address but remembering numbers is
very difficult for the people and also the IP addresses are not static
therefore, a mapping is required to change the domain name to IP
address. So DNS is used to convert the domain name of the websites to
their numerical IP address.
DNS is a hostname to IP address translation service. DNS is a distributed database implemented in a hierarchy of name servers. It is an application layer protocol for message exchange between clients and servers.
Name servers
Domain Name Servers (DNS) are the Internet's equivalent of a phone book. They maintain a directory of domain names and translate them to Internet Protocol (IP) addresses. This is necessary because, although domain names are easy for people to remember, computers or machines, access websites based on IP addresses.
DNS record
A domain name, IP address what is the validity?? what is the time to live ?? and all the information related to that domain name.
Once you understand the DNS
Host(Deploy) your website to Amazon EC2 or Heroku and obtain Public IP.
Buy a domain from domain provider like Godaddy
Map domain(ie www.example.com to IP)-> DNS record
Mapping domain to IP may vary platform to platform but the Core principle remains the same. I would suggest you these below link. Try to find differences in both, doing so you will learn along the way
http://www.littlebigextra.com/map-domain-name-amazon-aws-ec2-instance/
https://medium.com/progress-on-ios-development/connecting-an-ec2-instance-with-a-godaddy-domain-e74ff190c233
I'll get straight to the point.
I have bought a domain. I want to host it on my computer, maybe on a raspberry pi since only 50 persons/month will visit it.
Anywhere I've looked I see two hosting methods, using IIS/WAMP/XAMPP to only create a localhost website or adding the domain to C:\Windows\System32\drivers\etc\hosts.txt that is also... localhost.
What is the magic answer here? How can I host LIVE a website with the domain that I have bought? Am I stuck to using a hosting service? Am I missing something really important?
using IIS/WAMP/XAMPP to only create a localhost website
You need an HTTP server if you want to host a website. It needs to run on the computer you want to host the website from.
adding the domain to C:\Windows\System32\drivers\etc\hosts.txt
That's what you do as a poor man's solution instead of buying a domain name.
The Domain Name needs to be associated with a DNS server (and secondary DNS server) by your registrar.
Usually, a registrar will provide DNS hosting services as part of the deal.
The DNS server needs an A record pointing at the IP address of the computer running the web server. This IP address needs to be available to whomever is going to visit it (which almost certainly needs to be public facing) and should be static (unless you want to play games with very short TTL values and frequent reconfiguration of the DNS servers).
If you plan to host multiple different websites on the same server, you'll probably want to configure the HTTP server software to handle Virtual Name Hosting (whereby it pays attention to the Host header in the request and dynamically serves different content based on it)
I recently setup a domain name server on my ubuntu machine and added my DNS record for my website, question is how to make my domain name accessible to the public without the public having to add my dns server on their machine's configuration.
Unfortunately, this typically requires spending money at a DNS site, e.g. name.com, namecheap.com, GoDaddy (bad juju), etc.. Depending on the domain, you're going to probably spend at least $10/year. Unfortunately this bureaucratic system (run somehow by ICANN) is a result of the government's role in shaping the internet.
So I configured an authoritative name server after reading pages after pages of text regarding the standards of the server and its security. Question is how do I make my server accessible to the public such that they don't need to add my name server to their network configuration in order to access domains registered to that name server? I already have a domain name registered for that name server through a third party domain name provider.
Your registrar will have a way to make your DNS server authoritative for your domain. Look in their control panel for DNS options. When you register your domain they will set the DNS servers to their own, which you can change later. When you set your DNS servers it will take a bit for it to update, so if it doesn't happen right away just wait an hour or so. You should also flush and register DNS on the machine you are trying to access the site from.
FYI - you got down voted because stackoverflow is for programming and not server config questions.
Okay, can't seem to find a great article or info on this. My client purchased a domain for his company (domain.com) through Network Solutions. He has a local server running Windows 2008 R2 that he wants to host his company's website on. I've created the website and have it running with Apache on localhost. The server does have a static IP, but when I visit it, I'm prompted for credentials (user, password) which is expected as it's meant to be protected.
My question:
How would I point the domain to the website on his server?
From what I've researched, I have options that include:
Pointing the domain to the static IP (what about the credentials?)
Creating A and CNAME records for the DNS server on Network Solutions
Setting up a local DNS server w/ Active Directory on the Windows machine
Creating a couple name servers that would tell Network Solutions
where to send the domain
It's safe to say I'm effectively confused, so any help would be very much appreciated.
So basically you have to associate the domain name to the IP address, and that is done using DNS.
I'd suggest option 2 where you let Network Solutions manage the DNS, and you create an A record for www.domainname.com that points to the IP address on your server. Keep in mind it might take 24-48 hours for this new record to propagate across the internet. Take a look at http://www.networksolutions.com/support/dns-manager-advanced-tools/ and http://www.networksolutions.com/support/a-records-ip-addresses/
Regarding the credentials prompt, I assume you are using IIS and so you'd want to check the Authentication settings for the site. If you want anonymous access to the site, you would enable it there.