- Server operating system version
- Debian 13
- Plesk version and microupdate number
- 18.0.76.4
Experiencing some strange issue with certain (not all) domains; a zone transfer will only happen if done manually.
If I run (on the master dns server, which is using plesk)
it will transfer the zone from the master to the slave (which is just a plain linux server running bind). But if I make a change within the panel, it sends a NOTIFY, but never follows up with an XFER, which does happen when transferring manually. The zone on the slave server remains as it used to be until it's manually retransferred with every modification.
This applies only to 'some' domains which leads me to conclude something's off in the plesk database (after all my migration was botched and manually patched up). I just can't... find anything that would point me into a direction here.
Could it be something to do with SOA serial numbers? I did try to manually set those and plesk bin dns repair them. After manual transferring all the domains they do seem to match now (as does anything else in the zone file), but the problem still persists.
If I run (on the master dns server, which is using plesk)
Code:
/usr/sbin/rndc -b " ${master_ip}" -s "${slave_ip}" -p "953" -y "rndc-key" -c "/opt/psa/var/modules/slave-dns-manager/slave_${slave_ip}.conf" retransfer $domain
it will transfer the zone from the master to the slave (which is just a plain linux server running bind). But if I make a change within the panel, it sends a NOTIFY, but never follows up with an XFER, which does happen when transferring manually. The zone on the slave server remains as it used to be until it's manually retransferred with every modification.
This applies only to 'some' domains which leads me to conclude something's off in the plesk database (after all my migration was botched and manually patched up). I just can't... find anything that would point me into a direction here.
Could it be something to do with SOA serial numbers? I did try to manually set those and plesk bin dns repair them. After manual transferring all the domains they do seem to match now (as does anything else in the zone file), but the problem still persists.