Difference between revisions of "Split DNS (Zimbra)"

Jump to navigation Jump to search
m (Minor tweaking)
m (→‎DNS Records: Slight rewording of CNAME text)
Line 17: Line 17:
#* <code> 158.25.34.124 </code> is the static IP address assigned by your ISP.  You'll need to set-up a NAT on your router (often oddly called a virtual server in domestic routers) to map incoming mail on TCP 25 to your email server's actual address (EG <code> 158.25.34.124:25 -> 192.168.1.150:25 </code>).
#* <code> 158.25.34.124 </code> is the static IP address assigned by your ISP.  You'll need to set-up a NAT on your router (often oddly called a virtual server in domestic routers) to map incoming mail on TCP 25 to your email server's actual address (EG <code> 158.25.34.124:25 -> 192.168.1.150:25 </code>).


Note, instead of an A record, some people will use a CNAME record instead (though obviously the CNAME record will still need to point to a valid A record.)  Using a CNAME might be preferable, if for example you've multiple services running from a single public IP, that you might want to split out in the future to run on separate IP's, at which point you can replace the CNAME records with A records.  However, I've seen a number of pages on the internet suggesting you shouldn't do this and it may not work.  Therefore you're probably best not to.
Note, instead of an A record, some people will use a CNAME record instead (though obviously the CNAME record will still need to point to a valid A record.)  Using a CNAME might be preferable, if for example you've multiple services running from a single public IP, that you might want to split out in the future to run on separate IP's, at which point you can replace the CNAME records with A records.  However, I've seen a number of pages on the internet suggesting you shouldn't do this and it may not work, so if you're experiencing issues when using a CNAME consider changing to an A record.


== Localhost DNS Server Setup ==
== Localhost DNS Server Setup ==