• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Issue Slave DNS servers not updating zone from target server after migrating domain from source server.

BigBlock

New Pleskian
Server operating system version
ubuntu 22
Plesk version and microupdate number
Plesk Obsidian 18.0.67
I'm having an issue with: Slave DNS servers not updating zone from target server after migrating domain from source server.

I have a new Plesk server (target) setup and am trying to migrate all domains from the old server (source).
Both slaves (ns1 & ns2) are set up on both source and target servers, verified and communication is working fine. I can see notifies from both source and target in both ns1 & ns2 logs.
If a migrated domain DNS is modified in any way on source, both slaves get notified and send the transfer request. (works perfect)
If a migrated domain DNS is modified in any way on TARGET, both slaves get notified and neither slave sends a transfer request.

I have double checked that domains being migrated have A records pointing to the slave servers and complimentary NS records pointing to the A records.
ns1.<domain> A 3.97.30.209
ns2.<domain> A 3.96.121.139
...and the matching NS records...
<domain>. NS ns1.<domain>.
So the really annoying part is that out of five migrations, 2 resolve, transfer and update properly with the slaves - the other 3 do not...

At a loss as to what to look at next.
 
Hello!

Could you clarify a few things:

  1. What happens when you press Extensions > Slave DNS Manager > Resync (as seen in the screenshot)? Do you receive any messages, errors, or warnings?
  2. Have you run the following command?
Code:
plesk repair dns

These details might help in diagnosing the problem further.
 

Attachments

  • Screenshot.png
    Screenshot.png
    37 KB · Views: 1
Hello!

Could you clarify a few things:

  1. What happens when you press Extensions > Slave DNS Manager > Resync (as seen in the screenshot)? Do you receive any messages, errors, or warnings?
  2. Have you run the following command?
Code:
plesk repair dns

These details might help in diagnosing the problem further.
Same behavior from both the source and target servers, notifies are sent, only the source receives a transfer request. no errors or warnings on bind logs on any of the 4 servers...
 
increasing the log verbosity does now show that notifies are being refused:

```
26-Feb-2025 11:00:36.414 general: info: zone _domain_.com/IN: refused notify from non-primary: _ns1_#60939
26-Feb-2025 11:00:36.414 general: info: zone _domain_.ca/IN: refused notify from non-primary: _ns1_#46639
26-Feb-2025 11:04:06.095 general: info: zone _domain_.com/IN: refused notify from non-primary: _DESTINATION_#34709
```
Curious that the slaves are also sending notifies to the other slaves - been happening probably since day 1 but probably does not matter.
 
Back
Top