Quote:
Originally Posted by westendRIOT The website and email using the same domain name is giving me problems with DNS. Outlook (or Zimbra Desktop, or whatever) is configured with mydomain.com as the email server. |
It is incorrect to use the domain name for your mail server records. As I've already said - follow the instructions in the Split DNS article.
My local DNS points mydomain.com to the local IP for my Zimbra. Then, when one of my workstations tries to go to mydomain.com using their web browser (to reach the externally hosted website), the DNS server catches it and sends them to Zimbra's internal IP.
I tried setting the Zimbra server as mail.mydomain.com, so that Outlook, etc. uses the FQDN as the email server. This would allow web browser requests for mydomain.com hit the forwarders as described in the article you linked to, and use an external DNS entry to reach the externally hosted web server.
Quote:
Originally Posted by westendRIOT |
That's because you didn't follow the instructions when you initially installed Zimbra, you would have been asked if you wanted to change the domain name and at that point you should have said "yes" and set the correct domain name for the server.
Quote:
Originally Posted by westendRIOT Is it possible to configure finer granularity with the DNS forwarding? Like to send certain protocol or port requests to one IP vs another? |
It isn't needed, you just need to configure your DNS & server correctly and according to the wiki article. Your internal records should resolve the FQDN of the server to your LAN IP and your web site records should not resolve via your LAN DNS server and be forwarded to an external DNS resolver (and therefore get to your web server).