![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192282
http://bugzilla.opensuse.org/show_bug.cgi?id=1192282#c9
--- Comment #9 from Dr. Werner Fink
1. A Real Time Clock has nothing to do with RealTime scheduling.
2. I don't think that these time windows in DNSSEC are so tight that real time scheduling would make any difference.
3. At first glance I don't see any syscalls asking for RealTime scheduling in dnsmasq, so I guess enabling it in the kernel for the process would not change anything.
Is there any indication that the transient failures you are seeing are caused by missed time windows?
What I see ... after some sorting for domain and unified output Nov 04 10:07:03 tux dnsmasq[32292]: Insecure DS reply received for blog, check domain configuration and upstream DNS server DNSSEC support Nov 03 12:33:06 tux dnsmasq[12211]: Insecure DS reply received for cloudflare.net, check domain configuration and upstream DNS server DNSSEC support Nov 03 12:40:01 tux dnsmasq[12211]: Insecure DS reply received for cloudfront.net, check domain configuration and upstream DNS server DNSSEC support Nov 03 12:03:10 tux dnsmasq[11580]: Insecure DS reply received for com, check domain configuration and upstream DNS server DNSSEC support Nov 04 10:43:55 tux dnsmasq[1532]: Insecure DS reply received for cookiepro.com, check domain configuration and upstream DNS server DNSSEC support Nov 04 09:24:04 tux dnsmasq[12211]: Insecure DS reply received for d.akamaiedge.net, check domain configuration and upstream DNS server DNSSEC support Nov 04 09:52:20 tux dnsmasq[32292]: Insecure DS reply received for de, check domain configuration and upstream DNS server DNSSEC support Nov 03 12:11:50 tux dnsmasq[12211]: Insecure DS reply received for eu, check domain configuration and upstream DNS server DNSSEC support Nov 04 11:16:05 tux dnsmasq[1532]: Insecure DS reply received for example.org, check domain configuration and upstream DNS server DNSSEC support Nov 03 16:51:43 tux dnsmasq[12211]: Insecure DS reply received for fastly.net, check domain configuration and upstream DNS server DNSSEC support Nov 04 11:11:45 tux dnsmasq[1532]: Insecure DS reply received for glb.paypal.com, check domain configuration and upstream DNS server DNSSEC support Nov 04 08:47:20 tux dnsmasq[12211]: Insecure DS reply received for io, check domain configuration and upstream DNS server DNSSEC support Nov 03 13:30:16 tux dnsmasq[12211]: Insecure DS reply received for l.google.com, check domain configuration and upstream DNS server DNSSEC support Nov 04 10:32:07 tux dnsmasq[1532]: Insecure DS reply received for net, check domain configuration and upstream DNS server DNSSEC support Nov 03 13:29:22 tux dnsmasq[12211]: Insecure DS reply received for network, check domain configuration and upstream DNS server DNSSEC support Nov 04 10:41:53 tux dnsmasq[1532]: Insecure DS reply received for org, check domain configuration and upstream DNS server DNSSEC support Nov 04 11:08:54 tux dnsmasq[1532]: Insecure DS reply received for paypal.com, check domain configuration and upstream DNS server DNSSEC support Nov 04 11:46:48 tux dnsmasq[1532]: Insecure DS reply received for paypalcorp.com, check domain configuration and upstream DNS server DNSSEC support Nov 04 08:44:11 tux dnsmasq[12211]: Insecure DS reply received for slackb.com, check domain configuration and upstream DNS server DNSSEC support Nov 04 09:48:10 tux dnsmasq[12211]: Insecure DS reply received for uk, check domain configuration and upstream DNS server DNSSEC support Nov 04 09:20:46 tux dnsmasq[12211]: Insecure DS reply received for vodafonemail.de, check domain configuration and upstream DNS server DNSSEC support Nov 04 11:27:22 tux dnsmasq[1532]: Insecure DS reply received for x.akamaiedge.net, check domain configuration and upstream DNS server DNSSEC support -- You are receiving this mail because: You are on the CC list for the bug.