0

Kubuntu NextDNS service forgets to wake up(?)

Excuse me Please:

 

sorry for the ambiguous title, as am unsure as to how to simply describe this problem:

on cold-boot of a Kubuntu 2204 system,

with installed NextDNS service v1.47.1,

I find I can not connect to the Internet, namely, Firefox does NOT display webpages.

I can, however, ping to 8.8.8.8 without issue.

running the 'nextdns status' command results in a "running" response.

but no browsing.

issuing the command: nextdns restart

however,

DOES restore browsing.

What need I do to assure the nextdns service "WAKES! UP!" with the OS? ;)

5 replies

null
    • R_P_M
    • 21 hrs ago
    • Reported - view

    Could you test out a dig command while in this odd state. Also is Firefox the snap version?

      • Christopher_H
      • 20 hrs ago
      • Reported - view

       

      sure; umm, "dig"?

      also, now I am a bit shamed, as cold-booting the system in question, NOW is working. 😖

      (also, a detail i think may be relevant, but, no longer applicable: previously was working through a OPNsense router when oddities occurred. now having removed OPN and restored the Gl-iNet router, things seem to be working. rather doubt the devices would affect, but,... this may be beyond my understanding(s)) 🤷‍♂️

      • R_P_M
      • 17 hrs ago
      • Reported - view

       The dig command is used in terminal and usually follows this pattern:

      dig a www.domain.com

      This will return a IPv4 address for the entered domain. Other options are available for the dig command, see dig -h for a summary (a long summary it seems!).

      • Christopher_H
      • 5 hrs ago
      • Reported - view

       

      ceyarrecks@5479:~$ dig www.google.com

      ; <<>> DiG 9.18.39-0ubuntu0.22.04.3-Ubuntu <<>> www.google.com
      ;; global options: +cmd
      ;; Got answer:
      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29499
      ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

      ;; OPT PSEUDOSECTION:
      ; EDNS: version: 0, flags:; udp: 65494
      ;; QUESTION SECTION:
      ;www.google.com.                        IN      A

      ;; ANSWER SECTION:
      www.google.com. 50 IN A 192.0.0.88

      ;; Query time: 65 msec
      ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
      ;; WHEN: Sat Apr 11 09:09:45 EDT 2026
      ;; MSG SIZE  rcvd: 59

      🤷‍♂️

      • Christopher_H
      • 3 hrs ago
      • Reported - view

       also.

      I can not seem to reproduce said previous 'odd' state,... which, again, leads me to think there was some (weird?) relationship with the aforementioned OPNsense router.

Login to reply

Content aside

  • 3 hrs agoLast active
  • 5Replies
  • 22Views
  • 2 Following