NextDNS CLI backup on DNS2?

So for about a year, I've used NextDNS's IPv4 Linked IP setup on my home router.  It's worked decent, however, at times I cannot get pages to load... Long story short, I'm not sure if it's DNS or cable internet related.

Recently, I've set up the NextDNS CLI on a Linux box I have set up in the basement.  I've set up my wireless router to point to my Linux box for DNS1. 

Does it make more sense to leave DNS2 blank, or point DNS2 to one of the IPv4 linked IPs?

Right now, I've pointed DNS2 to the IPv4 linked IPs to see if all of my traffic is coming in from the NextDNS CLI... It is not... it looks like about half my traffic comes from DNS1 and the other half comes from DNS2.

Is there some sort of load balancing being done here?

3 replies

    • R_P_M
    • 1 mth ago
    • Reported - view

    It’s dependent on device, some may well do load balancing.

    For the second dns you can always repeat the first Linux box IP, as long as it’s reliable you won’t see any problems. 

    • Corey
    • 1 mth ago
    • Reported - view

    Would there be any adverse affect pointing DNS1 to the CLI (Linux box is always running) and DNS2 to one of the IPV4 linked addresses?

    Is there any speed advantage to using the CLI vs IP linked addresses?

      • R_P_M
      • 1 mth ago
      • Reported - view

       Speed wise would really be location dependent. It will be the difference between ultralow and the Anycast for your connection.

      The main difference between CLI and IPv4 addresses is that your requests are encrypted as apposed to open to be “snooped” at by any third party in between.

      There shouldn’t be any adverse effects if you do decide to set the IPv4 address as dns2.

Content aside

  • 1 mth agoLast active
  • 3Replies
  • 77Views
  • 2 Following