JasonM
Members
-
Joined
-
This was my output: # dig @127.0.0.1 google.com ; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> @127.0.0.1 google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33845 ;; 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 ; COOKIE: ffc3245ab568ee35 (echoed) ;; QUESTION SECTION: ;google.com. IN A ;; Query time: 1151 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Sep 08 06:31:18 CDT 2020 ;; MSG SIZE rcvd: 51 # I also verified that equinox.io resolves in a browser. Appears to be something with the Docker network. You've given me something to work with. Thanks again!
-
Thanks for the containers. I'm hoping you can point me in the right direction. I've been using regular Pi-hole for a very long time. I have a br0 custom network and all containers have their own IP. Of course, unRAID points itself at an external DNS. As far as I can tell, I have everything set up correctly, However, when I try to use either the DoH container or the Pi-hole/DoH container, I cannot get DNS resolution. Here's the log from the standalone DoH container. This is all it does after the container starts. [36mINFO[0m[2020-09-07T12:29:43-05:00] Version 2020.8.2 [36mINFO[0m[2020-09-07T12:29:43-05:00] GOOS: linux, GOVersion: go1.14.7, GoArch: amd64 [36mINFO[0m[2020-09-07T12:29:43-05:00] Environment variables map[config:/etc/cloudflared/config.yml proxy-dns:true proxy-dns address:0.0.0.0 proxy-dns-port:53 proxy-dns-upstream:https://1.1.1.1/dns-query, https://1.0.0.1/dns-query] [36mINFO[0m[2020-09-07T12:29:43-05:00] Adding DNS upstream - url: https://1.1.1.1/dns-query [36mINFO[0m[2020-09-07T12:29:43-05:00] Adding DNS upstream - url: https://1.0.0.1/dns-query [36mINFO[0m[2020-09-07T12:29:43-05:00] Starting DNS over HTTPS proxy server on: dns://0.0.0.0:53 [36mINFO[0m[2020-09-07T12:29:43-05:00] Starting metrics server on 127.0.0.1:45489/metrics [36mINFO[0m[2020-09-07T12:29:43-05:00] Autoupdate frequency is set to 24h0m0s [31mERROR[0m[2020-09-07T12:29:53-05:00] update check failed: Post "https://update.equinox.io/check": dial tcp: lookup update.equinox.io on 127.0.0.11:53: read udp 127.0.0.1:35256->127.0.0.11:53: i/o timeout Any ideas as to what I'm doing wrong? Thanks!
-
After updating from 6.7.2 to 6.8.0-rc1, Intel PRO/1000 VT Quad Port (EXPI9404VT) fails to get IP address. Server not reachable via static address, and setting to DHCP results in self-assigned IP.
-
I initially installed RC4 in place of 6.6.6 to address an issue I was having with the LSIO NVIDIA plugin. However, the issue seems to be related to unRAID itself. When I install the NVIDIA unRAID 6.6.6 build, disks connected to my Rocket 750 PCIe SATA controller are not recognized. This can be replicated even with no GPU installed, so the GPU isn’t the problem. If I revert back to vanilla unRAID 6.6.6, the disks come back. Even with a GPU installed, booting under vanilla, all drives come up. BIOS settings look good as far as I can tell and I've gone as far as to backup and nuke my USB to start from scratch. Same result. On recommendation from the NVIDIA support forum, I upgraded to RC4 (vanilla, not NVIDIA version,) but had the same issue. I nuked the USB again and installed RC3 with the USB Creator. It hung for a very long time while booting, so I dusted off a display, keyboard and mouse to see what was going on. The messages it hags on are all related to the 750. Once boot completes, it also take forever for emhttp to start. Between the two hangups, we're talking 5+ minutes to boot. The drives attached to the 750 did not show up. I upgraded in the unRAID web UI from RC3 to RC4 with the same result. I nuked the USB again, installed 6.6.6 via the USB Creator, booted normally with all drives recognized. Upgraded directly to RC4 from the web UI, and got the same result as above. None of these were the NVIDIA builds, and none of them had any config files carried over. They were all clean. So it seems the 750 is just not cooperating with 6.7 at the moment. I reverted to 6.6.6 and all is back to normal. I'm tagging this as urgent since the Rocket 750 is used in the 45Drives Storinator and user impact may be significant. If this is improper, mods please advise.