0

Has anyone successfully set up NextDNS on a rack server?

Hi all,

I'm setting up NextDNS on a rack-mounted server for a high-traffic environment and would love some advice. Has anyone here done the same? Specifically, I’m looking for tips on optimizing it for performance and handling large numbers of DNS queries.

Here are a few things I’m curious about:

Any specific hardware recommendations (CPU, RAM, network interfaces) for running NextDNS on a rack server under high load?

What settings or tweaks did you use to optimize NextDNS for speed and reliability in a high-traffic environment?

Did you implement caching or load balancing to improve performance? Any useful configurations for handling large volumes of DNS queries?

Any security tips (e.g., firewall settings) or monitoring tools to track performance and troubleshoot issues?

How did you scale NextDNS for redundancy and ensure uptime during peak loads?

Any insights or tips would be much appreciated! Thanks in advance.

set up NextDNS on a rack server?

2 replies

null
    • Calvin_Hobbes
    • 2 wk ago
    • Reported - view

    That’s what their service does for you.  You don’t operate the servers, they do.  If you want to run your own servers, you might look into PiHole.

    • Marco_Mendoza
    • 13 days ago
    • Reported - view

    Assuming you're working with the NextDNS router version.

    As far as I know, I previously asked about deploying NextDNS on a cluster of DNS proxies within the same network, but it appears that this functionality isn't currently supported. If you're considering using NextDNS for DNS caching, you might need to adjust various time-related settings to optimize performance:

    • cache-max-age
    • cache-size
    • max-ttl
    • timeout

    It seems that setting up multiple NextDNS servers isn't currently supported, as it functions as a standalone unit. Tweaking configuration values might offer some workarounds, but it's unclear how effective they'll be. Perhaps exploring a solution involving Squid proxy-cache could be a viable alternative, allowing for more customization and control.

    Regarding the hit/miss counter, it's exact meaning and customization options remain somewhat obscure. While the Syslog provides some information, it's not granular enough for detailed analysis. Manually logging and processing data is a cumbersome workaround, and doesn't provide much insight into NextDNS's internal workings.

    Given these limitations, it's worth considering if NextDNS is the optimal solution for your mid-sized business environment, especially if you require advanced features like those offered by Cisco Umbrella. While NextDNS might be well-suited for home and SOHO networks, its scalability and customization options for larger deployments may be limited.

Login to reply

Content aside

  • 13 days agoLast active
  • 2Replies
  • 43Views
  • 3 Following