Browse Source

Clarify README around MX Records

Added note to #3 to clarify MX Records cannot point to a CNAME or Alias but there is a work around discussed in this commit where you can create a second A record for subdomain.domain.tld and refer it to the IP address of your incoming mail server.
pull/116/head
gnubytes 4 years ago
committed by GitHub
parent
commit
da3b93bba3
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
  1. +4
    -1
      README.md

+ 4
- 1
README.md View File

@@ -45,7 +45,10 @@ give your full domain without any subdomain, i.e. `lukesmith.xyz`.
2. **A Let's Encrypt SSL certificate for your site's `mail.` subdomain**. 2. **A Let's Encrypt SSL certificate for your site's `mail.` subdomain**.
3. You need two little DNS records set on your domain registrar's site/DNS 3. You need two little DNS records set on your domain registrar's site/DNS
server: (1) an **MX record** pointing to your own main domain/IP and (2) a server: (1) an **MX record** pointing to your own main domain/IP and (2) a
**CNAME record** for your `mail.` subdomain.
**CNAME record** for your `mail.` subdomain. NOTE: You can't point an MX
Record to a CNAME or Alias BUT you can create a second A record for
subdomain.domain.tld (e.g. mail.lukesmith.xyz) and refer it to the IP address
of your incoming mail server.
4. **A Reverse DNS entry for your site.** Go to your VPS settings and add an 4. **A Reverse DNS entry for your site.** Go to your VPS settings and add an
entry for your IPv4 Reverse DNS that goes from your IP address to entry for your IPv4 Reverse DNS that goes from your IP address to
`<yourdomain.com>` (not mail subdomain). If you would like IPv6, you can do `<yourdomain.com>` (not mail subdomain). If you would like IPv6, you can do


Loading…
Cancel
Save