Why does the dkim_selector of the DKIM record for the domain in VestaCP not change?

Question

Domain Name System

Hello.
I want to make a DKIM record with a custom dkim_selector in the Vesta panel so that it can be used simultaneously with Yandex.Connect (formerly PDD), but after changing the selector in exim.conf, restarting the server and adding a new domain with the "Mail support" checkbox checked, in DNS weighs the old default selector mail._domainkey.
In this case, the value of this entry itself is added without quotes and v=DKIM1.

A similar problem is observed on a freshly installed version of the panel.
CentOS 7, nginx+php-fpm+exim.
How to live on or what am I doing wrong? :)

Answer 1

For all questions related to the operation of the VestaCP panel, it is better to contact the developer forum .
They respond quickly, on the same day you will receive a solution to your problem.

Answer 2

I think everything is trite just mail._domainkey. is registered in the DNS config generator And exim has nothing to do with it at all.
You need to see where Vesta generates this file and change the template in it.
For example, in ispconfig3 this crap is displayed in the admin panel with presets and there are no such questions. I
have never tinkered with the news, but the principle is the same, there is a generation template engine.
Nobody will get into your exim to read something there.