Updating root zone file bind
BIND 9.6 and 9.7 included files with the same keys in a slightly different format.
We are not providing updated files for these releases as they are well past end-of-life.
This re-priming can occur no more frequently than once per second due to the way The additional re-priming queries should not adversely affect your server's recursive performance and administrators will be unaware that they are occurring unless they are seeing checkhints warnings in their logs.
Note particularly that a resolver will only need to send queries to the root nameservers for a Root priming is done for the first time, only when named needs to send a query to one of the root nameservers.
Thus the root hint zone is assumed to be mostly accurate, but they are not treated as the authoritative list of the roots.ISC provides a file that contains the root key and the DLV key.(note that the DLV has been decommissioned and we recommend updating resolver configurations that query the DLV) Note: these are managed keys, so this is only applies the first time you execute named.When handling a client query for which it has no answer, a recursive server needs to know which authoritative server is responsible for the domain of the name it has been asked to resolve.
So for example, if a client queries for hostname.example.com, a recursive server that has just been restarted will not know where to find the authoritative servers for example.com, nor the authoritative servers for com.When this happens, named cannot trust the new set because they have not come from one of the authoritative root nameservers, so initiates a new root-priming event to ensure that it is using the correct set.