• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Set IP for primary DNS server via CLI returns error

AlbertoPizzarelli

New Pleskian
Server operating system version
Centos 7.9
Plesk version and microupdate number
18.0.54.3
hello,

after last update of plesk i'v got an error when add on my slave DNS server a primary ip, from CLI:

Code:
 /usr/local/psa/bin/./dns -a {DOMAIN} -primary 139.162.183.247
Unsupported DNS record type: ""

the bug is corrected on GUI interface but remain on CLI

plesk version
Product version: Plesk Obsidian 18.0.54.3
OS version: CentOS 7.9.2009 x86_64
Build date: 2023/08/07 10:00
Revision: 834e427a288420a9d89019e1b6344e0f6ae2a6de


anyone have a suggestion?
 
Could you please make sure that the database content is consistent by running:
# plesk repair database -y
# plesk repair dns
Does the issue persist after these repairs?
 
Code:
root@ns2 ~ # plesk repair db -y

Checking the Plesk database using the native database server tools .. [OK]

Checking the structure of the Plesk database ........................ [OK]

Checking the consistency of the Plesk database ...................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

root@ns2 ~ # plesk repair dns -y

Checking the DNS configuration file ................................. [OK]

Restoring DNS server configuration
    Synchronizing DNS zones with the DNS server ..................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0
 
I think I overlooked the "-a" in your initial command. Instead you were wanting to use "--set-master" if I am not mistaken. Please have a look at dns: DNS Zones on Domains for the correct syntax. That would be
plesk bin dns --set-master 139.162.183.247

The "-a" option is for adding a resource record.
 
I try to explain myself better, the problem arose when I updated to version 54, it was partially resolved, in fact now when I reate e new slave zone, and set for this zone primary master, it works, unfortunately I have always used this feature, but from the CLI , and from the latter the problem has not been solved,

DETAILS TO REPRODUCE THE ERROR: just create a new subscription, set the DNS as "SLAVE", and from the CLI go to set the primary master for that domain.
 
I think I overlooked the "-a" in your initial command. Instead you were wanting to use "--set-master" if I am not mistaken. Please have a look at dns: DNS Zones on Domains for the correct syntax. That would be
plesk bin dns --set-master 139.162.183.247

The "-a" option is for adding a resource record.
add what yor command convert simply a zone to master, Hehehehe, I think we're getting confused.
in any case I don't understand why my report was closed so quickly :-|
 
Could you please describe what you expected to happen when you execute
/usr/local/psa/bin/./dns -a {DOMAIN} -primary 139.162.183.247
?
 
Last edited:
@Kaspar I am probably just blind, could you please show me that example (e.g. by screenshot), because I am stuck with the "-a" command and the "-a" option, neither of which are linked to primary or secondary DNS settting. Where do you see the entry you are referring to?
 
o.k., got it, thank you. That looks like a parser error for that command, because the -a is also used as an option. I'll try to explain it accordingly in the issue report then.
 
Back
Top