Named slave zone not updating
db.cachedirectory /var/named secondary 18.104.22.168 bak.secondary 249.249.192.192.249.249.3 bak.192.249.249 secondary 253.253.192.192.249.249.3 bak.192.253.253 primary 0.0.127.db.127.0.0 cache .db.cache, since on rare occasions, we may have to delete all of the backup files manually. This means the slave has successfully loaded these zones from the primary master and saved a backup copy.It's also helpful to be able to tell at a glance that they're backup zone data files so that we're not tempted to edit them. To complete setting up your slave name server, try looking up the same domain names you looked up after you started the primary master server.This time, you must run to save a backup copy of the zone data.The crucial difference is where the server gets its data.
Each resource record can contain its own TTL value, which overrides this directive. The Cent OS project redistributes these original works (in their unmodified form) as a reference for Cent OS-5 because Cent OS-5 is built from publicly available, open source SRPMS.
Each zone file may contain directives and resource records.
Directives tell the nameserver to perform tasks or apply special settings to the zone.
The polling interval is one of those numbers in the SOA record that we haven't explained yet.
(BIND Versions 8 and 9 support a mechanism to speed up the distribution of zone data, which we'll describe later.) A slave name server doesn't need to retrieve all its zone data over the network; the overhead files, directory /var/named primary db.primary 249.249.192.db.192.249.249 primary 253.253.192.db.192.253.253 primary 0.0.127.db.127.0.0 cache .