search

outroll / vesta

VESTA Control Panel
http://vestacp.com
GNU General Public License v3.0
2.94k stars 1.03k forks source link

no trailing dot on DKIM record causes invaild record #1067

Open bhcopeland opened 7 years ago

bhcopeland commented 7 years ago

Operating System (OS/VERSION):

Ubuntu 16.04

VestaCP Version:

0.9.8

Installed Software (what you got with the installer):

--nginx yes --phpfpm yes --apache no --vsftpd no --proftpd no --exim yes --dovecot yes --spamassassin yes --clamav yes --named yes --iptables yes --fail2ban yes --mysql yes --postgresql yes --remi yes --quota no

Steps to Reproduce:

Add dkim record try dig mail._domainkey.example.me.uk TXT @ns1.example.me.uk +short edit dns template, and add "." to the domainkey restart bind run dig again, results returns ok

Edit: The problem only comes out when you disable dkim, and then re-enable it. A fresh domain seems to work okay. Once you edit the DNS record etc, you need to go in and add the "dot" to get the record to appear in dig.

Related Issues/Forum Threads:

https://forum.vestacp.com/viewtopic.php?f=12&t=13528&p=56345#p56345

bhcopeland commented 7 years ago

Every time I add a dns record, I have to go into the dns .db file, and add a full stop to the domainkey to make it valid.

Is this bug going to get some attention?