0

UDM PRO (UniFi OS Version 3.0.20 & Network Application 7.4.156) - - Inconsistent State on NextDNS v1.39.4 CLI

Good day all-

Appreciate any insight or assistance:

UDM PRO

UniFi OS Version 3.0.20

Network Application 7.4.156)

NextDNS v1.39.4

- after installation, from mobile on network WIFI browser states:
- This device is using NextDNS (from Firefox browser on mobile phone on WiFi network configured to use NextDNS)

On average of 1+ times a day receive notification from same browser, This device is not using NextDNS. This device is currently using 'AS-CHOOPA' as DNS resolver.

Action taken:

-Confirm nextdns is running (nextdns status)

-Implement nextdns activate

- Uninstall and -Reinstall (this has been done three times in a week). After this is done same Firefox browser confirms that I'm using NextDNS

At least once daily or sometimes several times a day receive confirmation that the DNS resolver has changed to 'AS-CHOOPA' ( 'This device is currently using 'AS-CHOOPA' as DNS resolver')

To resolve, re-enable SSH on UDM Pro in console
- Logging in via SSH using the published instructions and verify status again, sometimes several times in a row and it shows different statuses (running, not installed):

Presently its status is:

root@ZZZ:~# nextdns status
running
root@ZZZ:~# nextdns config
debug false
listen localhost:53
control /var/run/nextdns.sock
detect-captive-portals false
max-inflight-requests 256
profile 61b216
bogus-priv true
timeout 5s
setup-router true
auto-activate false
use-hosts true
log-queries false
max-ttl 5s
discovery-dns
mdns all
hardened-privacy false
cache-size 10MB
cache-max-age 0s
report-client-info true
root@ZZZ:~# nextdns status
not installed
root@ZZZ:~# nextdns status
not installed
root@ZZZ:~# nextdns status
running

I am using the current build. Is there a way to configure NextDNS via CLI to check to see if it's running and if it is not, to restart it?

Also https://test.nextdns.io results in (where 'MASKED' is listed below is blacked out as is PII):

"status": "ok",
        "protocol": "DOH",
        "profile": "MASKED",
        "client": "MASKED",
        "srcIP": "MASKED",
        "destIP": "MASKED",
        "anycast": false,
        "server": "zepto-sjc-1",
        "clientName": "nextdns-cli",
        "deviceName": "MASKED",
        "deviceID": "MASKED",
        "deviceIP": "MASKED",
        "deviceModel": "MASKED"

Appreciate the insight.

Thanks.

1 reply

null
    • R_P_M
    • 10 mths ago
    • Reported - view

    Was the test.nextdns.io done while in the “odd state” ? Also you don’t need to mask the destIP, that’s not PII, it’s the IP of the NextDNS PoP server you’re connected to.
     

    With regard to the nextdns status results, that’s a long standing bug with the CLI. It’s safe just to ignore it as it’s usually still running. If it only reports as “not installed” then there might be a problem. 

Login to reply

Content aside

  • 10 mths agoLast active
  • 1Replies
  • 342Views
  • 1 Following