daviditty
New member
Hi,
We're running our DA servers as autoprimary servers with PowerDNS as autosecondary, which then serve the zones as authorative servers to the world.
This way customers can manage their DNS zones via DA, which works perfectly fine, the IP's of the DA servers are configured as supermasters so they are allowed to push any zone, as long as it doesn't exist with another owner yet.
What I can't get my finger on is that when a user deletes a whole zone / package, the zone keeps existing on the PowerDNS servers, it seems that a notify for removing the zone is never sent?
This causes a lot of stale data in the database that is never to be used again, is there a way to configure Named so it does send a signal that the zone can be dropped?
Kind regards,
David
We're running our DA servers as autoprimary servers with PowerDNS as autosecondary, which then serve the zones as authorative servers to the world.
This way customers can manage their DNS zones via DA, which works perfectly fine, the IP's of the DA servers are configured as supermasters so they are allowed to push any zone, as long as it doesn't exist with another owner yet.
What I can't get my finger on is that when a user deletes a whole zone / package, the zone keeps existing on the PowerDNS servers, it seems that a notify for removing the zone is never sent?
This causes a lot of stale data in the database that is never to be used again, is there a way to configure Named so it does send a signal that the zone can be dropped?
Kind regards,
David
