• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved DNS values that are changed via the database are cannot be queried publicly until DNS Settings are saved in the GUI

tollube

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Version 18.0.60 Update Nr. 1
Hi, I am operating a small dynDNS service on my plesk server and I am updating the dns entries for a domain via php over the plesk database.
This works and the entry is set correctly. However I cant query that value and it gives back the old IP address until I change something and save it in the plesk GUI of the domain.
Do I need to somehow apply the new DNS values or am I missing something?
Thanks in advance!
Lukas
 
Rather than changing values in the Plesk database directly it's recommended to change them one of the programmable interfaces that are available to automate things. Like the Plesk CLI, REST API or XML-RPC API.
 
Thanks for your hint.
I did apply a quick workaround via XML API so that I don't have to rework the entire process.
So apparently these DB values are applied when you change something about the general dns settings for that domain.
So I apply values for the soa record and that seems to trigger the provisioning of the DNS entries in the plesk db.
Seems to work for me for now.
 
Back
Top