DNS resolver Stop Working after upgrade 2.4.5 to 2.5.0
-
Dear Team,
I have upgrade DNS resolver automatically Stop Working after upgrade 2.4.5 to 2.5.0. i have manually restart this service. Can you suggest.
-
See
https://forum.netgate.com/topic/84312/unbound-segfaults-signal-11?_=1613798935997 -
I have the same problem. DNS resolver stops after a few minutes.
Logfile (after I restarted 3 times):
Feb 20 10:11:56 dhcpleases 78457 Could not deliver signal HUP to process 74394: No such process.
Feb 20 10:11:36 kernel pid 74394 (unbound), jid 0, uid 59: exited on signal 11
Feb 20 10:07:44 dhcpleases 26574 Could not deliver signal HUP to process 81670: No such process.
Feb 20 10:07:36 dhcpleases 34430 Could not deliver signal HUP to process 81670: No such process.
Feb 20 10:06:36 kernel pid 81670 (unbound), jid 0, uid 59: exited on signal 11
Feb 20 10:04:48 dhcpleases 34430 Could not deliver signal HUP to process 52649: No such process.
Feb 20 10:04:36 dhcpleases 8162 Could not deliver signal HUP to process 52649: No such process.
Feb 20 10:03:36 dhcpleases 8162 Could not deliver signal HUP to process 52649: No such process.
Feb 20 10:02:50 kernel pid 52649 (unbound), jid 0, uid 59: exited on signal 11 -
Disabling "Register DHCP leases in the DNS Resolver" "solved" the problem.
-
@astronaut Ok I will try this option. And update you after some time.
Thanku so much. -
@mohdikramsaif I had the same issue and the same solution as above works. Thanks for having me waste 30 minutes to figure it out. Surprised this blunder made it to a 'stable' release.
-
@astronaut said in DNS resolver Stop Working after upgrade 2.4.5 to 2.5.0:
Disabling "Register DHCP leases in the DNS Resolver" "solved" the problem.
I ran it for about 18 hours with the setting disabled. No crashes. No trace of problems in the log file.
This morning I enabled "Register DHCP leases in the DNS Resolver" again. The router ran for abouter before the resolver crashed again. Thus the problem can be recreated at my end.
-
-
I got a similar problem with VLANs. My primary vlan runs without any problems. But every morning I boot up a PC within a different VLAN it can't lookup domains. Nslookup ends with a Timeout. After restarting the dns resolver it works immediately.
