[EMAIL PROTECTED] wrote: > To map the MX of example.com to client.com
example.com. IN MX 10 mail.client.com. Then configure mail.client.com to accept and deliver email for the domain example.com MX records point to hostnames, not to IP addresses, by the way. You point an MX to a hostname. And that hostname is defined as an A recor IN MX 10 frodo.hserus.net. And in the hserus.net zonefile frodo.hserus.net. IN A 204.74.68.40 Then the mailserver at frodo.hserus.net is configured to accept email for lists.linux-delhi.org and further process it (in this case, deliver it to a mailman mailing list). If you need multiple mailservers to handle email for the client.com domain there's MX priorities, and configuring the mailservers on those to accept and either deliver (in the case of a primary mx), or store + forward (in the case of a backup mx) Lowest mx number = delivery goes to it first, its the primary mx. Say priority 10. Then the other three servers can be mapped with priority 20, 30 and 40. Though, if you have to ask all this I'd recommend at least one good primer on dns, such as the O'Reilly grasshopper book on dns and bind And then whatever howtos etc are needed to configure your mailserver to accept mail for multiple domains (virtual domains) ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ linux-india-help mailing list linux-india-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-india-help
