bug in server_dns CLI

[Tozz]

We use "server_dns" to configure a default DNS zonefile for new domains. I believe there is a shortcoming in this tool. The separator for this utility is the semicolon (. This happens to be the same separator as for DKIM keys. You guessed it, I need to add a DKIM key to the default zonefile template.

The command:

/opt/psa/bin/server_dns --set "NS,,ns1.example.com;NS,,ns2.example.com;TXT,default_domainkey,v=DKIM1; k=rsa; t=y; p=keyhere;"

Does not work, as Plesk believes the semicolons for the TXT DKIM field are separators for other records. I have been unable to find a workaround. Is this a bug?

Perhaps adding a flag to define the separator key is a wise idea?

I was also wondering if it is expected behavior that Plesk does not add the domain key to DNS once a DNS zonefile has been reset to default. Thus, when one resets its DNS zonefile to the system default DKIM no longer works.

 

[IgorG]

There is no DKIM automation in Plesk 11.5
Support of DKIM will be added in Plesk 12.
In order to use DKIM you can add corresponding TXT record manually in Plesk GUI using this wizard, for example - http://www.dnswatch.info/dkim/create-dns-record

 

[Tozz]

You say Plesk 11.5 has no DKIM support, but it has. It is able to sign DKIM mail, and it publishes the key to the DNS. So DKIM seems to work fine, except for "server_dns". This seems like server_dns was forgotten when DKIM was implemented in Plesk.

Also, although this is for me a DKIM related issue.. The semicolon is a valid character in TXT records, so server_dns is still broken even if officially DKIM support is not available. Because adding just any record containing a semicolon would fail. The semicolon is not limited to DKIM.