• 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.

Issue DNS bind proxy on Plesk

Rossanmol

New Pleskian
Hi,

I am trying to set a dns for specific domain to /etc/named.conf, however my changes are not being applied.

As I described in this post at serverfault (http://serverfault.com/questions/836681/named-conf-setup-for-domain-dns-forwarding):

I am trying to use a custom DNS(x.x.x.x) when making a curl command to google.com on the website.

I am using bind9, how would my named.conf look like to be able to achieve that?

This is the code I added:

Code:
zone "google.com" IN {
    type forward;
    forwarders { 172.21.2.1; };
    forward only;
};

How can I achieve that, when PLESK is installed?
 
Hi,

What exactly are you expect?
- that curl create connect to 172.21.2.1? In other words, local named response 172.21.2.1 for google.com? Will you use curl only at this server?
- that local named asks DNS at 172.21.2.1 for IP-address for google.com?
 
Back
Top