When a user requests a recordset, can bind9 perform a health check on whether the registered record set is reachable?
I registered two record sets, such as aaa.a 188.8.131.52 184.108.40.206 A
220.127.116.11 is actually a fake and unreachable. 18.104.22.168 is actually a normal address.
When I request the analysis of this recordset 'aaa.a' from bind9, can bind9 tell me which IP is normal?
(Describe the solution you'd like to see.)