Method 1: Compare the timestamp on the slave zone file with the system's current date. Compare that difference with the expire timer in the SOA record in the same zone file. If the difference is greater than the expire timer, then the zone is expired.
Method 2: Check the logs. Chris Buxton BlueCat Networks On May 3, 2011, at 11:53 PM, hugo hugoo wrote: > Dear all, > > Is there a way to check that a slave zone is expired? > I use dig in the following way to see that the zone is not responding on my > server...but is this due to the fact that the zone is expired or another > problem? > > dnszone002:/etc/bind/zones/slave# dig @localhost omega-pharma.be soa > > ; <<>> DiG 9.3.4 <<>> @localhost omega-pharma.be soa > ; (1 server found) > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26868 > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 0 > ;; QUESTION SECTION: > ;omega-pharma.be. IN SOA > ;; AUTHORITY SECTION: > . 518400 IN NS A.ROOT-SERVERS.NET. > . 518400 IN NS B.ROOT-SERVERS.NET. > . 518400 IN NS C.ROOT-SERVERS.NET. > . 518400 IN NS D.ROOT-SERVERS.NET. > . 518400 IN NS E.ROOT-SERVERS.NET. > . 518400 IN NS F.ROOT-SERVERS.NET. > . 518400 IN NS G.ROOT-SERVERS.NET. > . 518400 IN NS H.ROOT-SERVERS.NET. > . 518400 IN NS I.ROOT-SERVERS.NET. > . 518400 IN NS J.ROOT-SERVERS.NET. > . 518400 IN NS K.ROOT-SERVERS.NET. > . 518400 IN NS L.ROOT-SERVERS.NET. > . 518400 IN NS M.ROOT-SERVERS.NET. > > > - How can I see that it is because the zone is expired? > > - Is there a way to visualise all the zones that are expired (to make a > cleanup of the configuration) > > > Thanks for your feedback, > > Hugo, > > _______________________________________________ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
