Skip to content

Eduardo Broering

My feedback

5 results found

  1. 61 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Eduardo Broering commented  · 

    Workaround:

    I discover a way to do this configuration using the ***** DNS Manager to notify all servers in the cluster. But is very easy to implement this in a further update of ***** DNS Manager. This will be solve these two situations related:
    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/9045103-plesk-dns-clustering
    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/37996243-multi-master-dns-scheme

    Anyway, you can use this to others customers as a workaround for now. Have a lot of posts in forums asking for this.

    Let's go to 'gambiarra':
    - First, install ***** DNS Manager in both Plesk servers.
    - In /etc/named.conf put the same secret key in both servers:

    key "rndc-key" {
    algorithm hmac-md5;
    secret "[KEYHERE]";
    };

    - In options, add allow-new-zones and allow-transfer like below (changing [IPSLAVE] to you IP Address):

    options {
    allow-new-zones yes;
    ...
    allow-transfer { [IPSLAVE]; 127.0.0.1; };
    };

    - Change the lines:
    controls {
    inet 127.0.0.1 port 953
    allow { 127.0.0.1; } keys { "rndc-key"; };
    };

    - To:

    controls {
    inet * port 953
    allow { [IPSLAVE]; 127.0.0.1; } keys { "rndc-key"; };
    };

    - Exactly the same configurations have to be done in both servers, just changing [IPSLAVE] to the another one and vice-versa;

    -After these configurations, go to ***** DNS Manager and add the other Plesk server. Important: when the ***** DNS Manager suggest the configuration, change the field secret key to the same key used in the /etc/named.conf or don't will works.

    - Go to Tools ans Settings > DNS Zone templates > SOA registries templates and select the own server in the Main name server. For example, if you are in the dns1.example.com, select dns1.example.com. After that, go to dns2.example.com and do the same thing selecting dns2.example.com.

    - Apply this configuration to all DNS zones and it's done: when you create a domain in one server, the domain zone will bem automatically created in the other, if you change, the update will bem sent, if you delete, the domain zone will bem removed in both DNS servers.

    - In my case, I'm using another server (server c) without Plesk to be the third DNS server. It's works too, the configuration is the same, the only diference (but optional) is to put a notify no; inside options named configuration. This will stop the server c to send notify to another servers because it will not host any websites. The server C should be added in the both ***** DNS Manager too, using the same secret key;

    The only preoccupation about that solution is to change /etc/named.conf in lines that Plesk could be reset. Anyway, changing the /etc/named.conf and trying to reload and restart named from Plesk and command line no changes the named.conf. I test too obviously creating a new domain, and the named.conf do not replaced too. But the alert of the possibility exists in named.conf.

    So if the ***** DNS Manager do these configurations automatically in the next update, will be solve this preoccupation.

    An error occurred while saving the comment
    Eduardo Broering commented  · 

    Hello,

    Have another feature suggestion about this here: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/37996243-multi-master-dns-scheme

    Please vote there too.

    Plesk Admins: if it's possible, please unify the two features to not divide votes.

    Eduardo Broering supported this idea  · 
  2. 24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Eduardo Broering commented  · 

    Hello,

    Have another feature suggestion about this here: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/9045103-plesk-dns-clustering

    Please vote there too.

    Plesk Admins: if it's possible, please unify the two features to not divide votes.

    Eduardo Broering supported this idea  · 
  3. 164 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Eduardo Broering supported this idea  · 
  4. 1,283 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Eduardo Broering supported this idea  · 
  5. 72 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Eduardo Broering supported this idea  · 

Feedback and Knowledge Base