- 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.
At a loss as to what to look at next.
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.
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...ns1.<domain> A 3.97.30.209
ns2.<domain> A 3.96.121.139
...and the matching NS records...
<domain>. NS ns1.<domain>.
At a loss as to what to look at next.