Kubuntu NextDNS service forgets to wake up(?)

R P M 

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 

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

🤷‍♂️

Ceyarrecks W. (CAH) 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.

R P M 

alright, am back to /attempt/ or at least continue the OPNsense setup, and the same "forgetfulness' has occurred.

a 'forgetfulness' i might add, that is NOT present when connecting through a Gl-iNet router.

here is the CLI results:

ceyarrecks@CFSZ6-I:~$ dig
; <<>> DiG 9.18.39-0ubuntu0.22.04.3-Ubuntu <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24098
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;.                              IN      NS
;; Query time: 5 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Wed Apr 15 11:48:49 AST 2026
;; MSG SIZE  rcvd: 28

ceyarrecks@CFSZ6-I:~$ 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: SERVFAIL, id: 3735
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;www.google.com.                        IN      A
;; Query time: 3 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Wed Apr 15 11:49:00 AST 2026
;; MSG SIZE  rcvd: 43

ceyarrecks@CFSZ6-I:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=18.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=117 time=21.6 ms
^Z
[1]+  Stopped                 ping 8.8.8.8

ceyarrecks@CFSZ6-I:~$ ping www.google.com
ping: www.google.com: Temporary failure in name resolution

ceyarrecks@CFSZ6-I:~$ 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: SERVFAIL, id: 32903
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;www.google.com.                        IN      A
;; Query time: 3 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Wed Apr 15 11:49:26 AST 2026
;; MSG SIZE  rcvd: 43

ceyarrecks@CFSZ6-I:~$ nextdns status
running
ceyarrecks@CFSZ6-I:~$ nextdns restart

ceyarrecks@CFSZ6-I:~$ ping www.google.com
PING www.google.com (216.239.38.120) 56(84) bytes of data.
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=1 ttl=116 time=18.8 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=2 ttl=116 time=14.8 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=3 ttl=116 time=106 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=4 ttl=116 time=21.1 ms
^Z
[2]+  Stopped                 ping www.google.com

ceyarrecks@CFSZ6-I:~$ 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: 16140
;; 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.         5       IN      A       216.239.38.120
;; Query time: 2 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Wed Apr 15 11:50:37 AST 2026
;; MSG SIZE  rcvd: 59
ceyarrecks@CFSZ6-I:~$

Once the nextdns service is RESTARTED, browser loads web pages(you tube in this case)

Also, detail not-obvious in the above 'code' that once the nextdns service was restarted, and the ping to name issued, a NOTICEABLE amount of time(3-5sec.) elapsed before the first line of response was displayed.

which, seriously, with the nextdns service installed, DHCP set to get IP from whatever device is connected (either Gl-iNet or OPN) whichever device the Kubuntu 2204 system is connected to should NOT affect DNS resolution, as the installed service is supposed to handle DNS.🤷‍♂️

Any ideas would be greatly appreciated.

Thank you for the time taken to assist my understanding.

HCA

oh! p.s.

in updating the os, i see the option to update nextdns from 1.47.1 --> 1.47.2

this update, would not have any relation to the above, would it?