After removing slave IP it continues creating an allow-transfer with that IP in /var/named/chroot/etc/named.conf

[notlebowski]

2 years ago I added a 2nd slave IP this extension.
Soon after I removed that IP.

Currently I have only 1 IP configured and there is only 1 file in /usr/local/psa/var/modules/slave-dns-manager/ which is a file named slave_.conf

If I do a resync in slave-dns-manager it starts to create 2 IP entries in /var/named/chroot/etc/named.conf where it should only make 1

I do not know where it gets the info of that old IP.

[N8Solutions]

@notlebowski I have an open ticket with Plesk right now for the same exact thing. I had an IP added that, and was actively syncing the zones with, but have since removed it, and it is still syncing with the old server somehow as I can see it happening in real time via the server log.

[notlebowski]

I've written more here:
https://talk.plesk.com/threads/plesk-continues-to-write-deleted-slave-dns-server-in-var-named-chroot-etc-named-conf.356482/

I need a workaround more than that I need a fix for the script that orphanates the slave server.
I need it once in 4 years.

I have no idea where it is getting the info that it should still try to sync the server.
A Plesk process is writing that config.

[notlebowski]

Is no-one reading here? ever?