0

NextDNS CLI 1.10.1 has a high memory footprint problem

I created an LXC in Proxmox Virtual Environment to install NextDNS CLI for LAN DNS, which allocates 256MB of memory, but the NextDNS program will take up nearly 200MB each time, feeling that the memory footprint is a little high, is this reasonable?

The LXC system is CentOS 8 and only HastDNS is installed.

Finally I had to increase the memory of this LXC to 512MB. I think 256MB of memory is enough.

10 replies

null
    • olivier
    • 3 yrs ago
    • Reported - view

    What is the output of “nextdns config”?

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey 

      [root@NextDNS ~]# nextdns config

      config XXXXXXXX

      cache-max-age 0s

      detect-captive-portals false

      bogus-priv true

      use-hosts true

      log-queries false

      cache-size 10MB

      discovery-dns

      hardened-privacy false

      timeout 5s

      setup-router true

      control /var/run/nextdns.sock

      max-ttl 5s

      report-client-info true

      auto-activate true

      listen localhost:53

      • olivier
      • 3 yrs ago
      • Reported - view

      Carrot eggs you mention 1.10.1 specifically, does it mean you did not have this issue with older versions? I run 1.10.1 on my router, it takes 31MB of RSS.

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey Older versions have also been encountered, before I have restarted lxc to solve memory usage problems. But run for a while, memory usage will rise, I think the upgrade can be resolved, but the problem is still the same. You saw that picture, too, and he ran for a while before the occupancy rate increased.

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey Is running the "nextdns log" command and getting a lot of "doh resolve: context deadline exceeded" in the log related to this?
      The log results are attached.

      log.txt
      • olivier
      • 3 yrs ago
      • Reported - view

      Carrot eggs those are timeouts. Can you please run a https://nextdns.io/diag please?

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey https://nextdns.io/diag/4371fa90-6077-11eb-a7db-271a9e8abbd2

      • ericafterdark
      • 3 yrs ago
      • Reported - view

      Carrot eggs i had a similar issue with his new version. Same errors. Had to stop/start NextDNS because DNS lookups suddenly failed. I'm running this on Pop OS 20.10. It's possibly related to activating sleep mode of my laptop and connecting to a different Wi-Fi network after waking from sleep.

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey I turned on IPv6, did switching between IPv4 and IPv6 cause a timeout?

      • Carrot_eggs
      • 3 yrs ago
      • Reported - view

      Mango Tiger I installed Proxmox on HPE Gen10 Plus to turn on LXC to run NextDNS CLI without hardware sleep issues.

Login to reply

Content aside

  • 3 yrs agoLast active
  • 10Replies
  • 361Views
  • 3 Following