2,187
edits
Difference between revisions of "Split DNS (Zimbra)"
Jump to navigation
Jump to search
m
→Local Network DNS Server Setup: Minor rewording
(Initial creation - content from Zimbra page, plus updates) |
m (→Local Network DNS Server Setup: Minor rewording) |
||
| Line 72: | Line 72: | ||
== Local Network DNS Server Setup == | == Local Network DNS Server Setup == | ||
This is most appropriate to use if you have an existing internal DNS server, that internal clients are already using. Note that all clients | This is most appropriate to use if you have an existing internal DNS server, that internal clients are already using. Note that all clients | ||
of the DNS server will use it to resolve '''all''' addresses for the domain that your Zimbra server is on. So if your domain | of the DNS server will use it to resolve '''all''' addresses for the domain that your Zimbra server is on. So if your domain is <code>sandfordit.com</code>, all name resolution for that zone will be handled by it. So if you have a server on the internet (eg <code> www.sandfordit.com </code>, you will need to have a local record for it added to your DNS. Otherwise local clients will request a DNS resolution with your local DNS, which will simply respond that there is no such host, and the local client will be unable to connect. | ||
So if you have to create a new zone in order to get Split DNS working, you may need to add additional records that replicate existing public DNS records. If you already have a zone in your DNS server (which should already be up to date), or have no other address in that DNS domain, then this shouldn't be a problem. | So if you have to create a new zone in order to get Split DNS working, you may need to add additional records that replicate existing public DNS records. If you already have a zone in your DNS server (which should already be up to date), or have no other device address in that DNS domain, then this shouldn't be a problem. | ||
If you are in any doubt, installing a local DNS server on your Zimbra server is the safest way to proceed. Any problems you cause should be restricted to that server, and won't impact any other working servers. One of the biggest risks when tinkering with DNS is that records get cached, everywhere, so once you've fixed whatever problem you've caused, you may have to wait days for the fix to have rippled around. | If you are in any doubt, installing a local DNS server on your Zimbra server is the safest way to proceed. Any problems you cause should be restricted to that server, and won't impact any other working servers. One of the biggest risks when tinkering with DNS is that records get cached, everywhere, so once you've fixed whatever problem you've caused, you may have to wait days for the fix to have rippled around. | ||