• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Did /usr/local/psa/bin/dns change in August?

mr-wolf

Silver Pleskian
Plesk Guru
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Version 18.0.54 Update #4
I have a script running some 4 years which removes a TXT-record and then adds a new one.

It used the syntax:

/usr/local/psa/bin/dns --del ${DOMAIN} -txt '' -domain ${SUBDOMAIN}

Notice the double single quotes.
I never gave it the TXT-value, but still the record was removed. I never tested if it removed all of them.

Now all of a sudden I have to add the TXT-value as well.
I already adapted my script to this new behaviour, but I don't think it should have been changed.

Isn't it more powerful to delete all subdomains when an empty string is given?
 
Maybe that's been done, because else it is not clear which TXT record ought to be removed. I did not find references to a change in the documentation here, bbut it will be hard to find, because "txt", "dns", and other such abbreviations exists in the thousands in the database, so very hard to search for and find the right one.

But does it not seem more plausible the way it is done now?
 
Before it would remove all the TXT-records.
The only way to remove one now is by giving its value...

A DKIM-record contains special characters and it's quite hard to get the proper value in a bash-variable to get it deleted.

How it worked wasn't ambiguous at all.
It doesn't/didn't do anything if you don't give any "-txt " as parameter
Previously it would delete all TXT subdomain if you gave it: -txt ''
Now it always returns with an error.

I have my own opendkim-scheme with a central DNS-server which manages 2 TXT-records.
These get a new key regularly.
These keys get distributed to all servers (private/public).

I was suddenly getting double TXT-records and because all "slave servers" saw a mismatch they threw out the keys for the domains.

I had DKIM before Plesk implemented it.
Because my system still had advantages, like those rolling keys, and I put in some effort at the time, I stuck with it.
 
Back
Top