Created attachment 899977 [details] Unbound logs Description of problem: In some cases after boot unbound fails to resolve DNS queries. Unbound service is runnning, network is up (ping 8.8.8.8 is successful) and the queries are actually cached by unbound, yet there is no response. This issue goes away after few minutes. Version-Release number of selected component (if applicable): unbound-1.4.21-3.fc20.x86_64 How reproducible: occasionally Steps to Reproduce: [root@griffin ~]# unbound-control dump_cache | grep sme sport.sme.sk. 299 IN CNAME sport.sme.sk.cdn.cloudflare.net. sport.sme.sk.cdn.cloudflare.net. 299 IN CNAME varnish-lb.sme.sk. sme.sk. 299 IN SOA ns.petitpress.sk. hostmaster.mafra.cz. 2014052201 21600 7200 604800 300 sme.sk. 3599 IN NS ns2.mafra.cz. sme.sk. 3599 IN NS ns.petitpress.sk. www.sme.sk. 299 IN CNAME www.sme.sk.cdn.cloudflare.net. www.sme.sk.cdn.cloudflare.net. 299 IN A 162.159.254.46 www.sme.sk.cdn.cloudflare.net. 299 IN A 162.159.252.47 www.sme.sk.cdn.cloudflare.net. 299 IN A 162.159.255.46 www.sme.sk.cdn.cloudflare.net. 299 IN A 162.159.253.47 www.sme.sk.cdn.cloudflare.net. 299 IN A 162.159.254.47 msg www.sme.sk.cdn.cloudflare.net. IN A 32896 1 299 0 1 0 0 www.sme.sk.cdn.cloudflare.net. IN A 0 msg sport.sme.sk. IN AAAA 32896 1 299 0 2 1 0 sport.sme.sk. IN CNAME 0 sport.sme.sk.cdn.cloudflare.net. IN CNAME 0 sme.sk. IN SOA 4 msg www.sme.sk. IN A 32896 1 299 0 2 0 0 www.sme.sk. IN CNAME 0 www.sme.sk.cdn.cloudflare.net. IN A 0 msg varnish-lb.sme.sk. IN AAAA 32896 1 299 0 0 1 0 sme.sk. IN SOA 4 msg sport.sme.sk.dlv.isc.org. IN DLV 32899 1 3600 0 0 3 0 msg www.sme.sk.dlv.isc.org. IN DLV 32899 1 3600 0 0 3 0 msg sme.sk.dlv.isc.org. IN DLV 32899 1 3600 0 0 3 0 msg sme.sk. IN NS 32896 1 3599 0 1 0 0 sme.sk. IN NS 0 [root@griffin ~]# time dig sme.sk ; <<>> DiG 9.9.4-P2-RedHat-9.9.4-12.P2.fc20 <<>> sme.sk ;; global options: +cmd ;; connection timed out; no servers could be reached real 0m15.018s user 0m0.013s sys 0m0.005s Attaching unbound logs from the time when I experienced the issue. In other cases, after boot I can see following in logs: -- Reboot -- May 28 13:11:53 griffin runuser[1111]: pam_unix(runuser:session): session opened for user unbound by (uid=0) May 28 13:11:53 griffin runuser[1111]: pam_unix(runuser:session): session closed for user unbound May 28 13:11:53 griffin unbound-checkconf[1120]: unbound-checkconf: no errors in /etc/unbound/unbound.conf May 28 13:11:53 griffin unbound[1123]: May 28 13:11:53 unbound[1123:0] warning: increased limit(open files) from 1024 to 8290 May 28 13:11:53 griffin unbound[1123]: [1123:0] notice: init module 0: validator May 28 13:11:53 griffin unbound[1123]: [1123:0] notice: init module 1: iterator May 28 13:11:53 griffin unbound[1123]: [1123:0] info: start of service (unbound 1.4.21). May 28 13:14:01 griffin unbound[1123]: [1123:0] error: could not SSL_write crypto error:00000000:lib(0):func(0):reason(0) This time resolving worked OK, but perhaps can be useful to compare to attached logs. Actual results: Unbound does not resolve for a few minutes after boot/resume. Expected results: Should resolve right away, especially for entries which are cached.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.