0

yet another This device is not using NextDNS.

quick sitrep:

three systems, all running Kubuntu 2204 and NextDNS 1.42

All OS are up to date.

browsers WaterFox, FireFox, LibreFox report working NextDNS on two systems.

yet, on one system, FireFox, WaterFox, LibreFox complain of the above "not using" when on nextdns.io, which identifies "This device is currently using 'TerraTransit AG' as DNS resolver." (all browsers installed using either FlatPak or SNAP so ARE isolated from each other.)

 

(also, if i understood what i was doing on the ADMINACCOUNT, System Settings/Network, i MANUALLY set the DNS to 45.90.28.241 and 45.90.30.241; but i am uncertain as to how to get the OS to display if it is actually using these, or, which DNS settings as one could in Windows using the CLI command: ipconfig /all which would detail the OS' configured DNS)

 

here are CLI details of NextDNS:

=========================================

ADMINACCOUNT@5479:~$ sh -c "$(curl -sL https://nextdns.io/install)"
INFO: OS: ubuntu
INFO: GOARCH: amd64
INFO: GOOS: linux
INFO: NEXTDNS_BIN: /usr/bin/nextdns
INFO: INSTALL_RELEASE: 1.42.0
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=c): c
NextDNS Profile ID (default=#################):
Sending your devices name lets you filter analytics and logs by device.
Report device name? [Y|n]: y
Accept DNS request from other network hosts.
Setup as a router? (y/n): n
Make NextDNS CLI cache responses. This improves latency and reduces the amount
of queries sent to NextDNS.
Enable caching? [Y|n]: y
Instant refresh will force low TTL on responses sent to clients so they rely
on CLI DNS cache. This will allow changes on your NextDNS config to be applied
on your LAN hosts without having to wait for their cache to expire.
Enable instant refresh? [Y|n]: y
Changes DNS settings of the host automatically when NextDNS is started.
If you say no here, you will have to manually configure DNS to 127.0.0.1.
Automatically setup local host DNS? [Y|n]: y
NextDNS installed and started using systemd init
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=c): e

=========================================

Usage: nextdns <command> [arguments]

The commands are:

install         install service init on the system
   uninstall       uninstall service init from the system
   start           start installed service
   stop            stop installed service
   restart         restart installed service
   status          return service status
   log             show service logs
   upgrade         upgrade the cli to the latest version
   run             run the daemon
   config          manage configuration
   activate        setup the system to use NextDNS as a resolver
   deactivate      restore the resolver configuration
   discovered      display discovered clients
   cache-stats     display cache statistics
   cache-keys      dump the list of cached entries
   trace           display a stack trace dump
   version         show current version

USERACCOUNT@5479:~$ nextdns version
nextdns version 1.42.0

USERACCOUNT@5479:~$ nextdns status
running

USERACCOUNT@5479:~$ nextdns log
Error: not supported

=========================================

(not supported?)

So.

I can not provide "log" information, for, some, reason.

Also, as two of the systems are IDENTICAL OS & Hardware,

this suggests there is a specific configuration issue on the one.

I would appreciate suggestions on additional tests i can run to track-down what is amiss on the one problem system.

28 replies

null
    • Christopher_H
    • 8 mths ago
    • Reported - view

    sooo,... no guidance from the gurus on additional tests i can perform to determine the source of the above DNS use confusion?

      • R_P_M
      • 8 mths ago
      • Reported - view

       As I suspected  NextDNS CLI has already activated automatically after the reboot. (You setup auto activate at install)

      Computer is now using NextDNS, hooray! It’s all working as it should be. 
      Problem solved! It was that immutable bit on the resolv.conf file which was stopping things from working.

       

      As for sudo command, it does not ask for a password again until after around 5 minutes have passed but it’s still required to be used before any command you want elevated privileges for. The session version of sudo is actually “su” and will raise all subsequent commands to super user level (to use it I think it has to be set up as a single command on its own. Never had to use it before so not entirely sure of the specifics).

      To find out about any command people usually use the man page to find out more details (not all commands have a man page though but most do). 
      Just use:

      man <command>

      It’s been very useful for me for many years.

      • Christopher_H
      • 8 mths ago
      • Reported - view

       

      Thank you SOOOOO much for the Guided Tour(?) down the Rabbit's Hole™

      I believe the point need-be made, that i made ZERO changes to this system from one day to the next, that with each daily cold-boot, there had been green, to then the one day, none, hence this forum chain.

      I would ask what caused this "i" to appear, as personally, myself did not implement it.

      Also ought the now removed "i" be re-instated to assure something awry does not happen (again)? 

      (and while i am aware of the 5,000 different MANuals, with their 5,000 pages of text; *I* do not have the ability to ingest, let alone, understand such vast quantities of information.)

      • R_P_M
      • 8 mths ago
      • Reported - view

       The immutable bit should NOT be put back on the resolv.conf file. It shouldn’t be used on any configuration file.

       I can’t think of anything that might have set the immutable bit automatically. It’s very odd and rare thing to happen. I just hope no other configuration files have been set immutable as well. Maybe an idea to keep an eye on that device for any other problems. 

Content aside

  • 8 mths agoLast active
  • 28Replies
  • 1061Views
  • 2 Following