I have a script that executes rndc reload on secondary (slave) servers on the zones that are modified. This command returns success if the reload is queued successfully.
I wanted to know if there is a way I can get the status of the actual zone transfer without going through the logs itself. I want to be able to automatically handle the case when bind reload failed based on the error itself. Currently, I have to parse the logs to get the status of the zone transfer after executing rndc reload.
Can someone help me figure out how I can get the status of the zone transfer after executing rndc reload which is better than parsing the logs itself.
NOTE [to add more clarity]: I know notify can be used for master to communicate to the slave about a change. My question is about knowing if there is any way to get notified when the zone transfer initiated by the slave failed due to any reason without parsing the logs.
E.g. May be after notifying the slave, the master server died due to some reason. In this case, when the slave initiates a zone transfer, it would fail on getting the SOA record from the master. I want to get notified for these kind of errors that can happen during zone transfer without actually parsing the logs.
Let me know if more information is needed.
No comments:
Post a Comment