Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-16-2008, 12:03 AM
Advanced Member
 
Posts: 206
Default [SOLVED] Split_DNS: MX-record question (non direct mail delivery)

Hi,

we are going to test install ZCS in a non direct mail delivery environment.
(downloading mails with fetchmail/POP3 stored at different email-accounts
at different ISPs to our main account (e.g. info@mycompany.com) .


My idea is that in such an environment the mx-record ( MX 10 mail.mailhoster.com )
of our mailhoster will not change.


Question:
What MX-value should I define during installation of Zimbra and/or Slit-DNS(bind) ?


Thank's a lot

John
Reply With Quote
  #2 (permalink)  
Old 12-16-2008, 08:36 AM
Moderator
 
Posts: 1,027
Default

Quote:
Originally Posted by john99 View Post
Hi,

we are going to test install ZCS in a non direct mail delivery environment.
(downloading mails with fetchmail/POP3 stored at different email-accounts
at different ISPs to our main account (e.g. info@mycompany.com) .


My idea is that in such an environment the mx-record ( MX 10 mail.mailhoster.com )
of our mailhoster will not change.


Question:
What MX-value should I define during installation of Zimbra and/or Slit-DNS(bind) ?


Thank's a lot

John
John,

The Split DNS articles don't make it as clear as they ought, and I haven't taken the time to write a better one yet, but the simple answer is, your Zimbra box needs to be able to resolve its fully-qualified hostname to the ip address that it actually has on its subnet, whether DMZ or LAN or whatever. The reason for "Split DNS" is that in all likelihood it's the only box that should see that literal IP address when it does an mxlookup or nslookup or whatever; others should see the public IP address of the box, which is usually NATted from somewhere. That's why the easiest thing to do in most cases is to run bind9 on the local Zimbra box and point it to itself for DNS (with forwarders set up to handle everything else)--and that way the Zimbra box is authoritative TO itself, FOR itself, and the rest of the world simply has different information.

So set up that internal address so that your primary A, MX and PTR records all resolve back to that internal IP of the Zimbra box and you should be golden.
__________________
Cheers,

Dan
Reply With Quote
  #3 (permalink)  
Old 12-17-2008, 12:34 AM
Advanced Member
 
Posts: 206
Default

Thank you very much Dan!

John
Reply With Quote
  #4 (permalink)  
Old 12-17-2008, 08:04 AM
Moderator
 
Posts: 1,027
Default

Quote:
Originally Posted by john99 View Post
Thank you very much Dan!

John
You're welcome, John. I'll mark this thread solved for now, but don't hesitate to come back and let us know if you have any additional problems, or just come back and cheer if you don't! We like good news here too!
__________________
Cheers,

Dan
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.