• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Fixed DNS servers of Plesk suggestion

P

pesja

Guest
Fixed DNS servers or the Plesk suggestion

We use for al the domains on the linux- and w2k3 boxes the same DNS-servers, which we set into the Server DNS Section.

We added into this section 2 DNS-servers, namely ns1.xyz.com and ns2.abc.com.

Then we make a domain on the same server, called xyz.com and pointed into the DNS section of that domain the shared IP to ns1.xyz. By all the other domains we don't have to do that (of cource) because they pointed automaticly to de former DNS-servers. We use an external DNS-server (ns.abc.com) for redundancy.

This is different than Plesk suggests. They make for every domain a new DNS server IP pointed to ns.domain (in the server section) and (into the domain section) the pointed the domain with the NS statement to the ns.domain. I can understand that i keep these settings, and add only a fixed secondary DNS-server to the server DNS-settings.

Can somebody tell me wether the first one or the seccond one is better / faster / etc?
 
Back
Top