On 26 Jul 2015, at 20:12, Viktor Dukhovni <postfix-us...@dukhovni.org> wrote:

> On Sun, Jul 26, 2015 at 07:59:48PM +0200, DTNX Postmaster wrote:
> 
>> Make everything 'zed.grinta.net', forward and reverse, including your 
>> MX record, and create CNAME records for your convenience, such as mail 
>> client configuration. If you need an A apex record, just create that 
>> separately, don't use it for sending mail.
> 
> Read that carefully, the hostname in the MX record SHOULD NOT be
> a CNAME:
> 
>    Good:
> 
>       example.com IN MX foo.example.com.
>       foo.example.com. IN A 192.0.2.1
> 
>    Not good:
> 
>       example.com IN MX foo.example.com.
>       foo.example.com. IN CNAME bar.example.com.
>       bar.example.com. IN A 192.0.2.1
> 
> The second form is tolerated by most MTAs, but violates RFC
> reqirements to avoid CNAMEs on the right hand side of MX records.

Yes, that's why I am saying 'forward and reverse' before MX :-)

As in, specific to the original poster's configuration, the DNS lookup 
results should look like this;

==
$ host zed.grinta.net
zed.grinta.net has address 109.74.203.128
==
$ host 109.74.203.128
128.203.74.109.in-addr.arpa domain name pointer zed.grinta.net.
==
$ host grinta.net
grinta.net has address 109.74.203.128
grinta.net mail is handled by 10 zed.grinta.net.
==
$ host smtp.grinta.net
smtp.grinta.net is an alias for zed.grinta.net.
zed.grinta.net has address 109.74.203.128
==

Mvg,
Joni

Reply via email to