Unbound DNS will not start after upgrade this morning

Started by rickg3, September 25, 2020, 09:28:07 PM

Previous topic - Next topic
After upgrade this morning my Unbound DNS service refused to start. I eventually disabled it and went back to DNSMasq to get DNS going again.

This past month I had setup three sets of DNS Servers in the Custom.conf forwarding and removed the servers from General settings. It was working well and I had no problems until today when I upgraded.

Any tips on what I am doing wrong would be helpful.

Quoteserver:
forward-zone:
name: "."
forward-ssl-upstream:yes
forward-addr: 9.9.9.9@853   #Quad9
forward-addr: 149.112.112.112@853   #Quad9
forward-addr: 1.1.1.1@853   #CloudFlare
forward-addr: 1.0.0.1@853   #CloudFlare
forward-addr: 8.8.8.8@853   #Google
forward-addr: 8.8.4.4@853   #Google

I can't believe I am the only person that had this?

When you type in unbound under the System -> Settings -> Logs (backend / General) what do it return at the time stamp when you try to reactivate unbound?

October 06, 2020, 04:19:43 PM #3 Last Edit: October 06, 2020, 04:27:53 PM by hushcoden
No need custom options, just type your servers in Miscellaneous

Unbound Services log has following : [29349:1] info: generate keytag query _ta-4f66. NULL IN

Nothing in general log.

Note: above entry from Sep 25 when upgraded, no other logs and unbound refuses to start no matter how configured.

October 07, 2020, 03:55:43 PM #5 Last Edit: October 07, 2020, 03:58:12 PM by Superduke
FWIW, I have the same log entry.

That said, when I check the function of Unbound (or better put the DNS server, meaning me, using GRC Spoof)....everything comes back fine....


Here is an explanation of the message. https://lists.nlnetlabs.nl/pipermail/unbound-users/2018-March/005110.html

Have you tried starting unbound via command line to see what kind of error it returns?

Quote from: rickg3 on October 07, 2020, 03:07:34 PM
Unbound Services log has following : [29349:1] info: generate keytag query _ta-4f66. NULL IN

Nothing in general log.

Note: above entry from Sep 25 when upgraded, no other logs and unbound refuses to start no matter how configured.