I came into a struggle the last few days.
Using WAMP Server and following this Tutorial I set up a local email environment, and I wanted to make the emails reach accounts outside of the local host.
I heard you need to make some changes in the DNS zone, so here is my DNS Zone at Freenom.
Is is possible to make emails sent from a computer using hMailServer reach the outside world through a domain?
Thank you for your time.
It is possible but it depends on your Scenario.
If you are behind a Router or a NAT or a Dynamic IP-Address it's almost not possible
to run a real World sending SMTP-Server and you shouldn't
If you have a Hosting plan (your own Windows V-Server or Root server) with Remote Desktop
access and a static ip address it's and access to the DNS-Configuration of your Internet Domain, it is possible and recommended.
1) First you need to setup a DNS A Record which points to your static IP in DNS
2) You need to create DNS MX Record which points to your A Record
Now you can add a new hMailServer Domain and add accounts and sent Emails
out. But you should setup a DNS A Record for IMAP or POP3 as well so you can
Receive Emails and not only sending.
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)
Is there a way to host mail server for certain domain on different machine.
For example:
If I own website.com and it is hosted on PC1 what are the requirements to make mail.website.com and host it on PC2.
I am planning to use Linux Ubuntu-postfix-squirrel mail...
This is fairly normal.
In your DNS config you'll specify one or more MX record types - these are the hosts responsible for handling mail for your domain. Note that they do not need to be hosts in your domain - ie, you can pay MS or Google for mail service, and you'd set your MX records to point to the MS or Google server.
Then for the website portion, normal A or CNAME records are used to point to a host.
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.
I have a web server that runs my web application.
If I want to outsource my email to another provider, is it possible if they are on their on network/data center?
Yes. To do this, you will need access to the DNS records for your domain. The MX record allows you to set up a mail server that's separate from the web server.
Google offers a service that will manage your domain's email through GMail, and the instructions on how to reconfigure your DNS for this service can be found here.
Yes, this is possible.
You need to use the combination of "A" record and "MX" record.
"A" record will point to your web server where your application is hosted.
"MX" record will point to the server where you want to host your email.
A complete step-by-step reference on how to do this can be found here Hosting website and emails on different servers
It is possible no matter where they are located, as long as you have control of your DNS records. I have run many sites where the web server is located in our building and the mail server is at the customer's own site, connected with via an unrelated ISP. In one case the web server is in the USA, and the mail server is in the UK.
The DNS records can be on a different server again. Some registrars include editing DNS records in their interface, others just let you set the DNS to another server.
The records that determine the e-mail server are called MX records. They take the name of the mail server (not it's IP address). The records that turn names to IP addresses are called A records - you use these for "www" etc.
Google Apps does just that.