[dkim_selector=x2] restore backup from old server 'x' to new server 'x2' DNS missing

[Ohm J]

After restore, 'x2._domainkey' record not created.
But click on button "RESET TO DEFAULT", 'x2' comeback to DNS record.

 

[zEitEr]

So you had 'x2._domainkey' in backups and it did not restore?

 

[Ohm J]

I move some user from the old server "x" record to the new server "x2" record.

 

[zEitEr]

So if you have "x" in backups why would it be turned to "x2" during the restore? If you used the option dkim_selector=x2, it is OK. But a directadmin server with "x2" do not expect to see "x" in backups, I believe.

Or do I totally misunderstand the case, and you had both "x2" in backups and dkim_selector=x2 in settings?

 

[Ohm J]

DA doesn't create the record "x2" during restore.
Because new server using "x2". Missing this record, the email won't send.

 

[zEitEr]

DA doesn't create the record "x2" during restore.

Did you restore a domain which had "x2" in a dns zone in backups? or the domain had "x" or even no domainkey record in backups?

 

[Ohm J]

Yes, old server only use the "x" key.
"x2" not have in the backup.

 

[zEitEr]

So, if you had "x" in backups it is expected, that directadmin does not transform it into "x2".

 

[Richard G]

I think @Ohm J needs a feature request.

To explain it in a more easier way maybe this helps.
We have this option when restoring via admin/backup transfer:

Restore with SPF values from backup. (unchecked: Use local spf values)

So one can choose wheather or not to use the SPF value from the backup.

Such option is not present for DKIM so one would expect that a new server would create new DKIM records automatically set to the dkim_selector which is set in the directadmin.conf file instead of using the ones from the backup.

Ofcourse this could overwrite custom dkim settings for other purposes, probably for that reason the ones from the backup are taken.

Since we DO have such choice option for nameservers and SPF, it would be good to -also- have such choice optoins for both DKIM selectors and DMARC settings.
So have the check or uncheck to either use from backup or use local values, same like with SPF and nameservers.

However, that would be a feature request.

 

[Ohm J]

@Richard G
Since this server using "x2", it should re-create the record with "x2".

Use "x" from the backup is useless and email sender doesn't work either, because I build the Exim with "dkim_selector=x2".

#But this issued can workaround by just create the backup without DNS record, or use "RESET TO DEFAULT" feature one by one for all domains.

 

[zEitEr]

It might be even a bug. I don't know what is behind the restore process. Does directadmin re-create a "x" record in DNS or simply copy/paste it from DNS zone dump.

 

[Richard G]

Use "x" from the backup is useless and email sender doesn't work either, because I build the Exim with "dkim_selector=x2".

Well then this is a bug, because a DKIM record should work no matter what the dkim_selector in the directadmin.conf says.
Because if it restores the dkim selector then it will also restore the DKIM key.

The dkim_selector setting in directadmin.conf is only for newly created DKIM keys. So if DA restores the x and the according key in that record, then Exim should just sign the mail with that DKIM key, same as you would create a custom DKIM key for something else. Should not cause any e-mail issues.
So if Exim is not signing with x then it's a bug.

Unless.....

Missing this record, the email won't send.

Do you really mean "not send" or do you mean that it will be refused by the receiving mailserver?
It if won't be send then what do the logs say?

You might want to remove the "solved" from the post in any case for now.

 

[Ohm J]

Email can send, but reject from the receiver.

Let's me show the sample

# grep -r 'dkim_selector' /etc/
/etc/exim.dkim.conf:  dkim_selector = x2

# cat /etc/exim.dkim.conf
#1.7
  dkim_domain = ${if \
                    eq{$sender_address_domain} {}\
                    {${lookup {${lc:${domain:$h_from:}}} lsearch,ret=key {/etc/virtual/domainowners}\
                        {$value}\
                        {$primary_hostname}\
                    }}\
                    {${lookup {$sender_address_domain} lsearch,ret=key {/etc/virtual/domainowners}\
                        {$value}\
                        {$primary_hostname}\
                    }}\
                }
  dkim_selector = x2
  dkim_private_key = ${if exists{/etc/virtual/$dkim_domain/dkim.private.key}{/etc/virtual/$dkim_domain/dkim.private.key}{0}}
  dkim_canon = relaxed
  dkim_strict = 0

This only config file to use dkim_selector = x2, that's required DNS record must be "x2".
And yes, it signed correct private key, but public key in the "{x}._domainkey" record missing.