LXC-container host unpopulated (DNS issue)?

Something wrong with the LXC template host?

Both me and my friend (so two different Omnias) are suddenly presented with an empty dropdown box at Luci > Services > LXC Containers:

Yep I installed my mSATA yesterday and was ready to try LXC, and find myself in the same situation. I was going to open a thread but I will use this one.

It’s again a DNS problem :confused:

Using kresd :

root@turris:~# dig A @127.0.0.1 +cd sks-keyservers.net

; <<>> DiG 9.9.8-P4 <<>> A @127.0.0.1 +cd sks-keyservers.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17946
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;sks-keyservers.net.            IN      A

;; Query time: 4009 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon May 22 22:06:49 CEST 2017
;; MSG SIZE  rcvd: 47

Using dnsmasq :

 root@turris:~# dig A @127.0.0.1 -p 5353 +cd sks-keyservers.net

; <<>> DiG 9.9.8-P4 <<>> A @127.0.0.1 -p 5353 +cd sks-keyservers.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26487
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;sks-keyservers.net.            IN      A

;; ANSWER SECTION:
sks-keyservers.net.     600     IN      A       37.191.226.104

;; Query time: 96 msec
;; SERVER: 127.0.0.1#5353(127.0.0.1)
;; WHEN: Mon May 22 22:07:00 CEST 2017
;; MSG SIZE  rcvd: 52

Ah thanks for clearing that up.

Anything concrete us newbies (me and my friend) can do to resolve this by ourselves,

any workarounds until it gets fixed by Cz.nic (presumingly at next update)?

Templates are probably downloading forom “repo.turris.cz/lxc

Could you check in LuCI > Status > System Log ou in ssh cat /var/log/messages if you have some errors like :
mvneta f1034000.ethernet eth1: bad rx status 8fa50000 (max frame length error), size=1504

My omnia was setup for an other provider with a custom MTU who wasn’t adapted for my new provider… so I had a lot of MTU error preventing kresd from working as it should…

Nothing of the like; have quite some warnings but those do not seem very sever nor related.

The good news: The containers are back (only a temporary “downage” of the server?)!

1 Like