0

Synology NextDNS Pegging CPU

I have NextDNS installed on 2 Synology NAS, I just installed today, one running 6.2.3-25426 Update 3 the other running  DSM 6.2.3-25426 Update 2.   On both of them, the CPU is now pegged at 100%, with NextDNS consuming almost all of the CPU on both NAS.  I also see multiple NextDNS processes running.  Attempting to stop Nextdns by running nextdns stop, does nothing.   Running top on the NAS, I can see "usr/local/bin/nextdns run"using all the CPU cores.   Rebooted one of the NAS, and NextDNS was normal, but after a few minutes, its back up to over 95% CPU usage.   This is making my NAS extremely slow servicing files or really for anything.  Anyone seen this and know of a resolution?

5 replies

null
    • Andy_Moser
    • 3 yrs ago
    • Reported - view

    To add to this, I am experiencing the same issues that I'm having on Raspberry PI with NextDNS in this post, https://help.nextdns.io/t/q6hz6na/nextdns-1-10-1-stops-working-on-raspberry-pis I have tried uninstalling NextDNS be rerunning the setup script and choosing uninstall. That fixes the CPU issue, but when I try to re-install Nextdns, I get errors that port 53 is already in use. I'm not running any other DNS or AD type services on this NAS, strictly ISCSI and a few shares. Config that I am using on NAS and Pi's is the same.

     

    2021-01-30T19:32:05-06:00 DS1621 nextdns[14200]: Startup failed: proxy: tcp: listen tcp :53: bind: address already in use

    2021-01-30T21:11:32-06:00 DS1621 nextdns[20240]: Startup failed: proxy: tcp: listen tcp :53: bind: address already in use

    2021-01-30T21:20:23-06:00 DS1621 nextdns[21914]: Startup failed: proxy: tcp: listen tcp :53: bind: address already in use

     

    If I run sudo netstat -tulpn I see port 53 is in use, but only by NextDNS, and only on IPV6 address.   If I uninstall NextDNS, I see nothing using port 53, but reinstalling it that is all I get in the nextdns log, bind: address already in use

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Andy 

      It is recommended to use Synology to create a virtual machine and then install nextdns in the virtual machine, the system is recommended to use centos, professional things to the professional virtual machine to do, allocate a small amount of hardware resources to nextdns on it such as 2 core CPU, 128M memory, 3G disk, so that even if nextdns failure, will not affect Synology's system.

      Then the device configuration DNS that requires DNS resolution points to the virtual machine.

      That's my suggestion.

      • Andy_Moser
      • 3 yrs ago
      • Reported - view

      Carrot eggs  Can you point me to the documentation on where that is suggested to use a VM vs native to DSM?   NextDNS provides instructions on how to directly install it on Synology native, no VM needed, which is what I prefer to do.   I'm assuming since NextDNS provides the documentation on how to do it, that it is supported.

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Andy https://www.synology.com/en-us/dsm/feature/virtual_machine_manager

      • Andy_Moser
      • 3 yrs ago
      • Reported - view

      Carrot eggs Thanks but I'm trying to run native on Synology per NextDNS documentation and not have to manage another set of VM's.  Running native normally consumes next to nothing as far as resources, I think this is a bug.

Login to reply

Content aside

  • 3 yrs agoLast active
  • 5Replies
  • 304Views
  • 2 Following