[GH-ISSUE #176] superdns in error loop #48

New issue

Closed

opened 2026-03-04 01:34:23 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:34:23 +03:00

Owner

Originally created by @rgov on GitHub (Jul 11, 2023).
Original GitHub issue: https://github.com/spr-networks/super/issues/176

My superdns container logs have tens or hundreds of MBs of entries:

[ERROR] Recovered from panic in server: "dns://:53" runtime error: invalid memory address or nil pointer dereference

The router (Clearfog) has a working Internet connection and DNS. Clients can route traffic to the Internet but cannot resolve DNS via the router.

; <<>> DiG 9.10.6 <<>> @10.0.0.1 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 710
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

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

;; Query time: 18 msec
;; SERVER: 10.0.0.1#53(10.0.0.1)
;; WHEN: Mon Jul 10 20:27:49 PDT 2023
;; MSG SIZE  rcvd: 39

Restarting the container, the full docker compose stack, or the entire router did not resolve the issue.

Originally created by @rgov on GitHub (Jul 11, 2023). Original GitHub issue: https://github.com/spr-networks/super/issues/176 My superdns container logs have tens or hundreds of MBs of entries: ``` [ERROR] Recovered from panic in server: "dns://:53" runtime error: invalid memory address or nil pointer dereference ``` The router (Clearfog) has a working Internet connection and DNS. Clients can route traffic to the Internet but cannot resolve DNS via the router. ``` ; <<>> DiG 9.10.6 <<>> @10.0.0.1 google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 710 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;google.com. IN A ;; Query time: 18 msec ;; SERVER: 10.0.0.1#53(10.0.0.1) ;; WHEN: Mon Jul 10 20:27:49 PDT 2023 ;; MSG SIZE rcvd: 39 ``` Restarting the container, the full docker compose stack, or the entire router did not resolve the issue.

kerem closed this issue

2026-03-04 01:34:24 +03:00

kerem commented

2026-03-04 01:34:24 +03:00

Author

Owner

@rgov commented on GitHub (Jul 11, 2023):

After rebooting my device clock was wrong. After syncing the clock DNS started working for clients.

I do not know if this was the initial problem.

@rgov commented on GitHub (Jul 11, 2023): After rebooting my device clock was wrong. After syncing the clock DNS started working for clients. I do not know if this was the initial problem.

kerem commented

2026-03-04 01:34:24 +03:00

Author

Owner

@lts-rad commented on GitHub (Jul 11, 2023):

@rgov i think so as the configuraiton uses dns over https which is time sensitive for certificate dates. i think we need to ensure the clearfog buildroot is running ntpdate to stay online.

@lts-rad commented on GitHub (Jul 11, 2023): @rgov i think so as the configuraiton uses dns over https which is time sensitive for certificate dates. i think we need to ensure the clearfog buildroot is running ntpdate to stay online.

kerem commented

2026-03-04 01:34:25 +03:00

Author

Owner

@lts-rad commented on GitHub (Oct 5, 2023):

the panic is fixed now at least and theres stacktraces with errors from dns if there is a panic now in the default config.

@lts-rad commented on GitHub (Oct 5, 2023): the panic is fixed now at least and theres stacktraces with errors from dns if there is a panic now in the default config.

kerem referenced this issue

2026-03-04 01:36:01 +03:00

[PR #48] [CLOSED] [ui] [build] Build the frontend for the native architecture #273

kerem referenced this issue

2026-03-04 01:36:01 +03:00

[PR #49] [MERGED] [build] Use buildx bake to make multi-platform images #274