diff --git a/README.md b/README.md index d9f506e1..ed2e5220 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ We're working on migrating [old wiki documents](http://www.iredmail.org/wiki) to Markdown format for easier maintenance, you can find converted documents [here](https://bitbucket.org/zhb/docs.iredmail.org/src). # Install iRedMail * [Install iRedMail on Red Hat Enterprise Linux, CentOS](https://bitbucket.org/zhb/docs.iredmail.org/src/default/installation/install.iredmail.on.rhel.md) -* [Setup DNS records for your mail server](https://bitbucket.org/zhb/docs.iredmail.org/src/default/installation/setup_dns.md) +* [Setup DNS records for your iRedMail server](https://bitbucket.org/zhb/docs.iredmail.org/src/default/installation/setup_dns.md) * [Perform silent/unattended iRedMail installation](https://bitbucket.org/zhb/docs.iredmail.org/src/default/installation/unattended.iredmail.installation.md) # How to * [Change mail attachment size](https://bitbucket.org/zhb/docs.iredmail.org/src/default/howto/0-change.mail.attachment.size.md) diff --git a/html/index.html b/html/index.html index 512e02d4..1e4a198f 100644 --- a/html/index.html +++ b/html/index.html @@ -12,7 +12,7 @@
NOTE: STILL WORKING IN PROGRESS
+IMPORTANT NOTE: A
, MX
records are required, Reverse PTR
, SPF
and
+DKIM
are optional but strongly recommended. All in all, set them all up please.
A
records map a FQDN (fully qualified domain name) to an IP address. This is
+usually the most often used record type in any DNS system. This is the DNS
+record you should add if you want to point a domain name to a web server.
Name
: This will be the host for your domain which is actually a computer
+ within your domain. Your domain name is automatically appended to your name.
+ If you are trying to make a record for the system www.mydomain.com
. Then all
+ you enter in the textbox for the name value is www
.
Note: If you leave the name field blank it will default to be the record
+for your base domain mydomain.com
. The record for your base domain is
+called the root record or apex record.
IP
: The IP address of your FQDN. An IP address can be thought of as
+the telephone number to your computer. It is how one computer knows how to
+reach another computer. Similar to the country codes, area codes, and phone
+number it is used to call someone.
TTL
: The TTL (Time to Live) is the amount of time your record will stay
+in cache on systems requesting your record (resolving nameservers, browsers,
+etc.). The TTL is set in seconds, so 60 is one minute, 1800 is 30 minutes, etc..
Systems that have a static IP should usually have a TTL of 1800 or higher. +Systems that have a dynamic IP should usually have a TTL of 1800 of less.
+The lower the TTL the more often a client will need to query the name servers +for your host's (record's) IP address this will result in higher query traffic +for your domain name. Where as a very high TTL can cause downtime when you +need to switch your IPs quickly.
+Sample record:
+NAME TTL TYPE DATA
+
+www.mydomain.com. 1800 A 192.168.1.2
+
+
+The end result of this record is that www.mydomain.com.
points to 192.168.1.2
.
PTR record or more appropriately a reverse PTR record is a process of resolving an IP address to its associated hostname. This is the exact opposite of the process of resolving a hostname to an IP address. Example, when you ping a name mail.somedomain.com it will get resolved to the ip address using the DNS to something like 192.168.1.5. Reverse PTR record does the opposite; it looks up the hostname for the given IP address. In the example above the PTR record for IP address 192.168.1.5 will get resolved to mail.somedomain.com.
-The most common use for looking up a PTR record is done by spam filters. Concept behind this idea is that fly by night spammers who send e-mails out using fake domains generally will not have the appropriate reverse PTR setup at the ISP DNS zone. This criterion is used spam filters to detect spam. If your domain does not have an appropriate reverse PTR record setup then chances are most e-mail spam filtering software will block e-mails from your mail server.
-You would most likely need to contact your ISP and make a request to create a reverse PTR record for your mail server IP address. For example, if your mail server is mail.somedoamin.com then ask your ISP to setup a reverse PTR record 192.168.1.5 (your internet public IP address) in their revesre DNS zone. Reverse DNS zones are handled by your ISP even though you may have your own forward lookup DNS zone that you manage.
+PTR record or more appropriately a reverse PTR record is a process of resolving
+an IP address to its associated hostname. This is the exact opposite of the
+process of resolving a hostname to an IP address (A
record). Example, when you ping a
+name mail.somedomain.com
it will get resolved to the ip address using the DNS
+to something like 192.168.1.5
. Reverse PTR record does the opposite; it looks
+up the hostname for the given IP address. In the example above the PTR record
+for IP address 192.168.1.5
will get resolved to mail.somedomain.com
.
The most common use for looking up a PTR record is done by spam filters. +Concept behind this idea is that fly by night spammers who send e-mails out +using fake domains generally will not have the appropriate reverse PTR setup +at the ISP DNS zone. This criterion is used by spam filters to detect spam. If +your domain does not have an appropriate reverse PTR record setup then chances +are email spam filtering softwares MIGHT block e-mails from your mail server.
+You would most likely need to contact your ISP and make a request to create a
+reverse PTR record for your mail server IP address. For example, if your mail
+server hostname is mail.somedoamin.com
then ask your ISP to setup a reverse
+PTR record 192.168.1.5 (your internet public IP address) in their revesre DNS
+zone. Reverse DNS zones are handled by your ISP even though you may have your
+own forward lookup DNS zone that you manage.
Mail Exchanger Record or more commonly known as MX record is an entry in the DNS server of your domain that tells other mail servers where your mail server is located. When someone sends an e-mail to a user that exists on your mail server from the internet, MX provides the location or IP address where to send that e-mail. MX record is the location of your mail server that you have provided to the outside world via the DNS.
-Most mail servers generally have more than one MX record, meaning you could have more than one mail server setup to receive e-mails. Each MX record has a priority number assigned to it in the DNS. The MX record with lowest number has the highest priority and that is considered your primary MX record or your main mail server. The next lowest mx number has the next highest primary and so on. You generally have more than one mail server, one being the primary and the others as backups.
-If your ISP or domain name registrar is providing the DNS service, you can request them to set one up for you. If you manage your own DNS servers then you need to create the MX records in your DNS zone yourself.
+Mail Exchanger Record or more commonly known as MX record is an entry in the +DNS server of your domain that tells other mail servers where your mail server +is located. When someone sends an e-mail to a user that exists on your mail +server from the internet, MX provides the location or IP address where to send +that e-mail. MX record is the location of your mail server that you have +provided to the outside world via the DNS.
+Most mail servers generally have more than one MX record, meaning you could +have more than one mail server setup to receive e-mails. Each MX record has a +priority number assigned to it in the DNS. The MX record with lowest number +has the highest priority and that is considered your primary MX record or +your main mail server. The next lowest mx number has the next highest primary +and so on. You generally have more than one mail server, one being the primary +and the others as backups, only one MX for mail server is OK too.
+If your ISP or domain name registrar is providing the DNS service, you can +request them to set one up for you. If you manage your own DNS servers then +you need to create the MX records in your DNS zone yourself.
If you found something wrong in this document, please do contact us to fix it.