0

EDNS (ECS) problem

I run the CLI on an ASUS router and always saw my ECS info I went to dnscheck.tools, but for the past few weeks the ECS info is missing.  I have removed and reinstalled the CLI, reset the router and tried different browsers but cant figure out what's going on.  If I use the NextDNS app or the profile directly on my devices the ECS info does come through, only the router CLI seems to have an issue.

27 replies

null
    • NextDNs
    • 2 wk ago
    • Reported - view

    How do you check EDNS is provided?

    • tnpapa.1
    • 2 wk ago
    • Reported - view

    I go to dnscheck.tools.     Here are two snaps showing what I see with using the profile and with using the CLI.  In the past both gave the same results.

      • NextDNs
      • 2 wk ago
      • Reported - view

      can you please provide a https://nextdns.io/diag in both config?

      • tnpapa.1
      • 2 wk ago
      • Reported - view

       Sent...  BTW this only became an issue after the latest update to the CLI for Merlin-ASUS.

      • NextDNs
      • 2 wk ago
      • Reported - view

       can you share the URLs of the diags and which one is which please?

      • tnpapa.1
      • 2 wk ago
      • Reported - view

       Not sure what you are asking. I ran your diagnostic in terminal and it sent them out.

      • tnpapa.1
      • 2 wk ago
      • Reported - view

       

      Using CLI.txt Using Profile.txt
      • NextDNs
      • 2 wk ago
      • Reported - view

       you have to wait for the diag to finish, at the end it will propose to post it and will give you back a URL.

      • tnpapa.1
      • 2 wk ago
      • Reported - view

       All I got was would you like to send this, and then the process ended and put me back at the prompt

      • NextDNs
      • 2 wk ago
      • Reported - view

      did you say yes? Didn't it give you a URL back?

      • tnpapa.1
      • 2 wk ago
      • Reported - view

       Ran it again.  This is using the CLI

      https://nextdns.io/diag/739831a0-ca16-11ef-936c-4704a0a1e372

      • NextDNs
      • 2 wk ago
      • Reported - view

       do you have the diag without CLI?

      • tnpapa.1
      • 2 wk ago
      • Reported - view

      https://nextdns.io/diag/74121660-ca33-11ef-bacf-3593e1be8fd7

    • tnpapa.1
    • 2 wk ago
    • Reported - view

    Is there a way I can roll back to the prior version of the CLI to test if that is the culprit for sure?

      • NextDNs
      • 2 wk ago
      • Reported - view

       try

      INSTALL_RELEASE=<some version> sh -c 'sh -c "$(curl -sL https://nextdns.io/install)"'
      • tnpapa.1
      • 2 wk ago
      • Reported - view

      I tried this: INSTALL_RELEASE=1.43.5 sh -c "$(curl -sL https://nextdns.io/install)"

      but it still installed 1.44.3

      • NextDNs
      • 2 wk ago
      • Reported - view

       use

      NEXTDNS_VERSION
    • tnpapa.1
    • 2 wk ago
    • Reported - view

    I rolled back to 1.43.5 and ECS is now working again as it should.

    • tnpapa.1
    • 2 wk ago
    • Reported - view

    https://nextdns.io/diag/ef72cb90-ca35-11ef-a5ea-0106201ae5e8

    working with 1.43.5

    • NextDNs
    • 13 days ago
    • Reported - view

    This change should fix your issue: https://github.com/nextdns/nextdns/commit/6af1300f554cb2fece7ff3fdd5836cb1f12b7b6b

      • tnpapa.1
      • 13 days ago
      • Reported - view

       Will give it a try once the family is off the Internet for the night just in case I have to reset the router.

      • tnpapa.1
      • 13 days ago
      • Reported - view

       Nope, ran the updater and brought it back to 1.44.3 and the ECS info is no longer being shown.  Rolled back again to 1.43.5 and ECS is back.

      • NextDNs
      • 13 days ago
      • Reported - view

       you would have to test the snapshot or wait for the next version to include this fix. The current version does not include the fix.

      • tnpapa.1
      • 13 days ago
      • Reported - view

       Thanks for all the help. I will stick to the older version for now and wait for a new future version. 1.43.5 seems to work just fine.

      • tnpapa.1
      • 7 days ago
      • Reported - view

        Has this fix been incorporated yet into the latest version?

Login to reply

Content aside

  • yesterdayLast active
  • 27Replies
  • 168Views
  • 3 Following