Dear, we use this api call (with several others call), in order to delete the zone from the ispconfig master. But today we saw that this call remove only the soa records, and not all the records of the zone, that they remains on the database. Is that normal??
Yes. In it#s current implementation, the API call deletes the zone only. But I agree that it would make sense to extend it in the future to do recursive deletes or at least stop with an error when there are still records in that zone.
oh damn, that a very strange move for this api. btw, now we have a lot of records on the master db that refer to an old server_id now removed from the stack (the zone are already move on new a server on the same master-slave stack, so with a different server_id). In order to clean up stuff, can we remove all the previous records of the table dns_rr querying from the server_id? example: delete * from dns_rr where server_id=[OLD-SERVER-ID-NO-LONGER-USED] ? ty
