Article ID: 121732, created on May 24, 2014, last review on May 24, 2014

  • Applies to:
  • Plesk Automation 11.5

Symptoms

PPA is set up with a master and slave DNS servers. DNS servers are hosted on an Amazon could services.

When DNS records are being added\changed in PPA, changes do no propagate to slave servers right away.

'/var/log/messages' on a slave server contains the alike errors:

May 24 06:04:24 ns2 named[25371]: zone domain.com/IN: refused notify from non-master: 1.1.1.1#58473

Where 1.1.1.1 is not a master DNS server IP address, though it is clear from '/var/log/messages' on master server, that notifies are being sent at the very same time.

Cause

Network communication between Amazon VM's is not transparent, so IP address is being replaced during network communication.

Resolution

Please contact Amazon support in order to clarify the networking issue.

As a workaround, you may decrease the "Refresh" interval in the DNS resource activation parameters to make zone refreshes more frequent. In this case, slave server will be initiating the transfer on its own, and therefore, query will not be denied.

  1. Access "Resources" menu
  2. Find and select "DNS" resource
  3. In "Activation parameters" click "Edit", and lover the value of "Refresh field"

Value should be specified in seconds.

Search Words

dns not syncing

33a70544d00d562bbc5b17762c4ed2b3 e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF