OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 21.1 Legacy Series »
  • DNSCrypt-Proxy + Unbound = need to restart service after the boot
« previous next »
  • Print
Pages: [1]

Author Topic: DNSCrypt-Proxy + Unbound = need to restart service after the boot  (Read 1818 times)

karlson2k

  • Full Member
  • ***
  • Posts: 111
  • Karma: 4
    • View Profile
DNSCrypt-Proxy + Unbound = need to restart service after the boot
« on: June 19, 2021, 05:16:00 pm »
Hello,

I have combination of DNSCrypt-Proxy + Unbound configured as described at https://docs.opnsense.org/manual/how-tos/dnscrypt-proxy.html and https://forum.opnsense.org/index.php?topic=10670.0.

The problem is uncoordinated starts of DNSCrypt-Proxy and Unbound.
During the boot process Unbound started usually before DNSCrypt-Proxy and even when DNSCrypt-Proxy is started, Unbound still fails to resolve addresses. This could be solved by manual restart of Unbound service, but it is quite annoying to manually restart Unbound after each reboot.

Could it be solved somehow?
Logged

blblblb

  • Newbie
  • *
  • Posts: 26
  • Karma: 2
    • View Profile
Re: DNSCrypt-Proxy + Unbound = need to restart service after the boot
« Reply #1 on: July 27, 2021, 10:54:55 pm »
+1 this is causing me issues too. I also replied to the thread about SERVFAIL responses that creep up over time.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 15589
  • Karma: 1347
    • View Profile
Re: DNSCrypt-Proxy + Unbound = need to restart service after the boot
« Reply #2 on: July 28, 2021, 09:12:18 am »
> The problem is uncoordinated starts of DNSCrypt-Proxy and Unbound.

For a rigid system and traceable bootup sequence "uncoordinated" is a strange word. If you rely with core tools like  Unbound on plugin tools such as Dnscrypt-proxy of course you will run into design obstacles for the simple fact that core tools are started before plugin tools.

If you just want to restart Unbound after Dnscrypt-proxy you can use the autostart described here:

https://docs.opnsense.org/development/backend/autorun.html

The "start" priority should be higher than 50 to let plugins start first, e.g. 60 is fine for the script. And the command to restart Unbound is:

pluginctl dns


Cheers,
Franco
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 21.1 Legacy Series »
  • DNSCrypt-Proxy + Unbound = need to restart service after the boot
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2