2,187
edits
Difference between revisions of "Split DNS (Zimbra)"
Jump to navigation
Jump to search
m
Minor tweaking
m (Minor rewording and Meta updates) |
m (Minor tweaking) |
||
| Line 1: | Line 1: | ||
[http://en.wikipedia.org/wiki/Split-horizon_DNS Split DNS] is required for Zimbra where your server is on an internal ([http://www.wikipedia.org/wiki/Private_network#Private_IPv4_address_spaces private address range]) network. | [http://en.wikipedia.org/wiki/Split-horizon_DNS Split DNS] is required for [[:Category:Zimbra|Zimbra]] where your server is on an internal ([http://www.wikipedia.org/wiki/Private_network#Private_IPv4_address_spaces private address range]) network<ref name="PrivAddr" />. | ||
Zimbra needs to be able to resolve its own Mail Exchanger (MX) DNS record, otherwise its services will not start. Therefore if your server is known publicly by one IP address, but in fact has a different internal address (and the public IP is NAT'ed to the internal IP) you'll need to use split DNS. This allows your server to be known by one IP address on the internet, and a different address internally, but with the same hostname regardless of where you are. There are two methods described below that enable you to achieve this... | Zimbra needs to be able to resolve its own Mail Exchanger (MX) [[Acronyms#D|DNS]] record, otherwise its services will not start. Therefore if your server is known publicly by one IP address, but in fact has a different internal address (and the public IP is [[Acronyms#N|NAT]]'ed to the internal IP) you'll need to use split DNS. This allows your server to be known by one IP address on the internet, and a different address internally, but with the same hostname regardless of where you are. There are two methods described below that enable you to achieve this... | ||
# [[#Localhost DNS Server Setup|Localhost DNS Server Setup]] - DNS server installed locally on the Zimbra server. | # [[#Localhost DNS Server Setup|Localhost DNS Server Setup]] - DNS server installed locally on the Zimbra server. | ||
# [[#Local Network DNS Server Setup|Local Network DNS Server Setup]] - DNS server on your local network, if you have one available. | # [[#Local Network DNS Server Setup|Local Network DNS Server Setup]] - DNS server on your local network, if you have one available. | ||
Note that Split DNS, Split-Horizon DNS, Split-Brain DNS all refer to the same technique, and the terminology can be used interchangeably. | '''Note that Split DNS, Split-Horizon DNS, Split-Brain DNS all refer to the same technique''', and the terminology can be used interchangeably. | ||
== DNS Records == | == DNS Records == | ||
| 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 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. Therefore you're probably best not to. | ||
== Localhost DNS Server Setup == | == Localhost DNS Server Setup == | ||
| Line 84: | Line 84: | ||
#* '''A record''' for your server's hostname and internal IP address | #* '''A record''' for your server's hostname and internal IP address | ||
#* '''MX record''', pointing to the A record just created | #* '''MX record''', pointing to the A record just created | ||
== Additional Notes == | |||
<references> | |||
<ref name="PrivAddr">For example, your Zimbra server may have an IP address of 10.0.1.5 or 192.168.3.7, but from the outside world its accessible via a public address such as 159.105.10.35</ref> | |||
</references> | |||
[[Category:Zimbra]] | [[Category:Zimbra]] | ||
[[Category:DNS]] | [[Category:DNS]] | ||