SPF entry is not created when adding a new domain

[wordpane]

When I'm creating a new domain, it's not creating the SPF TXT entry automatically, and when I try to create it manually, it tells me that the entry has been added, but it doesn't load the entry into the DNS table.

 

[wordpane]

When trying to activate DKIM through the control panel, no entry is added, but if I try to add entries of type A, CNAME, they work.

 

[Richard G]

Do you have any customisations made in templates or content in the /usr/local/directadmin/data/templates/custom directory?
Can you also check your /usr/local/directadmin/conf/directadmin.conf file if there is a dkim=1 or dkim=2 statement present?

 

[wordpane]

Do you have any customisations made in templates or content in the /usr/local/directadmin/data/templates/custom directory?
Can you also check your /usr/local/directadmin/conf/directadmin.conf file if there is a dkim=1 or dkim=2 statement present?

It is configured as dkim=2
There are no customizations in the custom folder.

 

[wordpane]

I did some tests and with and without customization in the custom folder, the problem is the same.

Is there something I can reset, as it seems to be only with this part of the dns, type A entries are registered correctly, but TXT does not work.

 

[Richard G]

Is there something I can reset

Not that I know of. However. is this a new server? If yes, how lang did you wait to try and configure things?
Did you waited until you got the message in the system messages that all background tasks were finished?

Because the DA installation itself is ready very quickly, but background installation takes longer (time is depending on vps/server speed/resources) and if you already start doing things before that, things can go wrong.

If it's new and only first, you can choose to install again and then wait. or maybe remove the domain and user (if it's not admin), then issue the build all command as root via SSH and see if it works then after all is finished.

 

[wordpane]

Not that I know of. However. is this a new server? If yes, how lang did you wait to try and configure things?
Did you waited until you got the message in the system messages that all background tasks were finished?

Because the DA installation itself is ready very quickly, but background installation takes longer (time is depending on vps/server speed/resources) and if you already start doing things before that, things can go wrong.

If it's new and only first, you can choose to install again and then wait. or maybe remove the domain and user (if it's not admin), then issue the build all command as root via SSH and see if it works then after all is finished.

It's a new server, but it was working normally, it just started recently, I don't remember what happened to cause this problem, I believe I will reinstall to solve this problem.

 

[Richard G]

I believe I will reinstall to solve this problem.

Maybe it's a bug in some new version, I don't know, didn't see anyone complaining yet, maybe a ticket could help you too.
Did you check logfiles from DA to see if it throws errors in that direction? Because re-installing might be more work than fixing if fixing is possible.
Also check your system logs for DNS errors.

 

[wordpane]

Maybe it's a bug in some new version, I don't know, didn't see anyone complaining yet, maybe a ticket could help you too.
Did you check logfiles from DA to see if it throws errors in that direction? Because re-installing might be more work than fixing if fixing is possible.
Also check your system logs for DNS errors.

Do you have the model of the zone that is saved in named.db? I want to do a test, but I'm not sure if mine is the standard, I was in doubt.

 

[Richard G]

You mean the one that normally is resident in the /usr/local/directadmin/templates directory? Yes.

|?SET_TTL=`DEFAULT_TTL`|
|?NS_TIME=`SET_TTL`|
|?A_TIME=`SET_TTL`|
|?MX_TIME=`SET_TTL`|
|?CNAME_TIME=`SET_TTL`|
|?PTR_TIME=`SET_TTL`|
|?TXT_TIME=`SET_TTL`|
|?AAAA_TIME=`SET_TTL`|
|?SRV_TIME=`SET_TTL`|
|?SPF_TIME=`SET_TTL`|
|?TLSA_TIME=`SET_TTL`|
|?CAA_TIME=`SET_TTL`|
|?DS_TIME=`SET_TTL`|
$TTL |SET_TTL|
@       IN      SOA     |NS1|      |EMAIL| (
                                                |SERIAL|
                                                |SET_TTL|
                                                3600
                                                1209600
                                                86400 )

|NS|
|A|
|MX|
|CNAME|
|PTR|
|TXT|
|AAAA|
|SRV|
|SPF|
|TLSA|
|CAA|
|DS|

Those are defaults, normally you can't mess those up. Never change things in the template directory directly anyway.