Bug 1180267

Description of problem:
unbound-anchor is not run in the right interval so our unbound package does not comply with RFC 5011:

http://tools.ietf.org/html/rfc5011#section-2.3 says:
   A resolver that has been configured for an automatic update of keys
   from a particular trust point MUST query that trust point (e.g., do a
   lookup for the DNSKEY RRSet and related RRSIG records) no less often
   than the lesser of 15 days, half the original TTL for the DNSKEY
   RRSet, or half the RRSIG expiration interval and no more often than
   once per hour.  The expiration interval is the amount of time from
   when the RRSIG was last retrieved until the expiration time in the
   RRSIG.  That is, queryInterval = MAX(1 hr, MIN (15 days, 1/2*OrigTTL,
   1/2*RRSigExpirationInterval))

Current DNSKEY TTL in root zone is 172800 seconds, i.e. 172800/60/60/24 = 2 days. It means that unboud-anchor should be run at least once a day.

Currently, unbound-anchor is run once a month instead of once a day.

Version-Release number of selected component (if applicable):
unbound-1.4.20-19.el7

How reproducible:
100 %

Steps to Reproduce:
1. look at /etc/cron.d/unbound-anchor

Actual results:
Currently, unbound-anchor is run once a month instead of once a day.

Expected results:
Current DNSKEY TTL in root zone is 172800 seconds, i.e. 172800/60/60/24 = 2 days. It means that unboud-anchor should be run at least once a day.


Additional info:
It might be better to convert cron job to systemd timer so it could get run once a day at random time. Currently it gets run at the very same time on all RHEL machines with the package. That could lead to spikes in network traffic ...