Validating, recursive, and caching DNS(SEC) resolver
bbc56d0b27
Once ntpdate.service is fixed to order itself After nss-lookup.target, there will be an ordering loop. To reproduce this do: [root@notas ~]# yum -y install unbound ntpdate chrony [root@notas ~]# systemctl enable ntpdate.service chronyd.service unbound-anchor.timer unbound.service unbound-anchor.service [root@notas ~]# systemd-analyze verify /usr/lib/systemd/system/* And then in the output you can find: Found ordering cycle on ntpdate.service/stop Found dependency on nss-lookup.target/start Found dependency on unbound.service/start Found dependency on unbound-anchor.service/start Found dependency on unbound-anchor.timer/start Found dependency on time-sync.target/start Found dependency on chrony-wait.service/stop Found dependency on chronyd.service/stop Found dependency on ntpdate.service/stop Signed-off-by: Tomas Hozza <thozza@redhat.com> |
||
|---|---|---|
| .gitignore | ||
| 0001-SOA-negative-TTL-is-capped-at-minimumttl-in-its-rdat.patch | ||
| 0001-Use-print_function-also-for-Python2.patch | ||
| 0002-libunbound-examples-produce-sorted-output.patch | ||
| 0002-Maximum-negative-TTL-patch-configparser-regeneration.patch | ||
| 0003-libunbound-Python-libldns-is-not-used-anymore.patch | ||
| 0004-Resolve-Python-3-incompatibilities-in-libunbound-and.patch | ||
| block-example.com.conf | ||
| dlv.isc.org.key | ||
| example.com.conf | ||
| example.com.key | ||
| icannbundle.pem | ||
| root.anchor | ||
| root.key | ||
| sources | ||
| tmpfiles-unbound.conf | ||
| unbound_munin_ | ||
| unbound-aarch64.patch | ||
| unbound-anchor.service | ||
| unbound-anchor.timer | ||
| unbound-keygen.service | ||
| unbound-munin.README | ||
| unbound.conf | ||
| unbound.munin | ||
| unbound.service | ||
| unbound.spec | ||
| unbound.sysconfig | ||