[bug] Unable to use DNS TXT records template with entry name _domainkey in DirectAdmin

MaXi32

Verified User
Joined
Jul 25, 2016
Messages
658
Location
The Earth
Just to inform you that this bug is easy steps to reproduce at the end of this post. I hope the DA team can provide an explanation for this issue, as it is similar to a bug I reported in 2021 related to using the API with no feedback. The original post can be found here: https://forum.directadmin.com/threa...onf-with-api-include-step-to-reproduce.63247/



In this post, I would like to report a bug when using a template from the following location when using DNS entry name _domainkey: /usr/local/directadmin/data/templates/custom/dns_txt.conf

/usr/local/directadmin/data/templates/custom/dns_txt.conf


Steps to reproduce (this is working fine):

1) Create a new custom template with the following contents
/usr/local/directadmin/data/templates/custom/dns_txt.conf

_domainkey_working="o=~; r=webmaster@|DOMAIN|"

Save the file and exit

2) To update the new records for a new domain, go to the following DNS page in your domain and click the link that says "Reset Defaults."

1678364255025.png




The output:

You will see a new TXT entry called _domainkey_working (this is working fine)


4) Now change this entry from dns_txt.conf in step 1) from

_domainkey_working="o=~; r=webmaster@|DOMAIN|"

to

_domainkey="o=~; r=webmaster@|DOMAIN|"


And click "Reset Defaults" again.

The output:

You will not see a new TXT entry called _domainkey (this is not working)

Note I can manually insert DNS TXT entry with _domainkey with no issue, it is just a template issue.


If this is not a bug, I would appreciate just an explanation for this issue of why a DNS entry with the name _domainkey does not appear in the DNS record but the other names are working fine. I need to use this entry name. Thank you.

@fln

Operating system: Debian 11
Affected DA version: latest stable v1.646
 
Last edited:
Back
Top