Jump to content

Lanraider

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by Lanraider

  1. For anyone (like me) who was still trying to install this:

     

    Its very easy to fix the command failed error just edit "--mac-address=00:00:00:00:00:00" field with your mac address that you find in your network settings. Then it will install and start, but i still didnt got it to work. Shame the support is in Discord as i dislike chats. 

    • Like 1
  2. On 2/3/2022 at 12:13 AM, gyto6 said:

    I'll add that you might be concerned about logs errors "due" to poor ressources for Unbound..

     

    Unless you've more than 500 workers in your network depending on your stuff, do not urge to set the container as "Priviledge" if only for home usage.

     

    What i noticed is that in the docker tab the container is still using port 53, instead of showing that it is using port 5335 (like put in the docker config) is this right?

     

    To me, it sounds like a false positive and refers to the out port for DNS request. In my own case, it solves DNS queries and is indeed listening my pihole request on port 5335.

     

    Thanks for your answer! 

     

    I had time again to play around a bit with unbound & pi-hole, so the pihole container was not set to "Priviledge" i think the "Maximum number of concurrent DNS queries reached (max: 150) error" was because i restarted the pihole container and it always forgets the DNS Settings i put in and changes to "listen to all devices", even though i put in "Allow only local devices" and another DNS Server it should use, when it starts again.

     

    So i tested unbound and i figured out that it is not using my pihole.conf file in the unbound.conf.d dir! Dont know why it is doing this... So i tested unbound with the unbound.conf that is in the unbound main dir and it is working fine and answering in the pihole query log with "sent to unbound.br0#5335" like i put it in the unbound.conf file. How can i say to unbound to use my pihole.conf file or how do i fix this?

     

    Another thing i noticed is that it is not using DNS over TLS with the unbound.conf, like with the pihole.conf file when it was recognised.

     

    Also i get the following errors in the unbound log:

     

    [1644065587] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:200::b port 53
    [1644065587] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:200::b port 53
    [1644065587] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:2d::d port 53
    [1644065587] unbound[1:0] warning: setrlimit: Operation not permitted
    [1644065587] unbound[1:0] warning: cannot increase max open fds from 40960 to 189120
    [1644065587] unbound[1:0] warning: continuing with less udp ports: 1750
    [1644065587] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning
    [1644065587] unbound[1:0] error: Could not open logfile /dev/null: Permission denied

     

     

     

     

     

    • Like 1
  3. 11 hours ago, Wozzagonebush said:

    Could someone share a working config of both unbound and pi-hole please? I have tried all the suggestions here but have not had any success.

     

     # dig pi-hole.net @127.0.0.1 -p 5335

    ; <<>> DiG 9.11.5-P4-5.1+deb10u6-Debian <<>> pi-hole.net @127.0.0.1 -p 5335
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached
    #

    Thats what i did:

     

    1. Put the container to brO

    2. Put an fixed IP in the optional field

    3. create an folder /mnt/user/appdata/unbound/

    4. Paste the path /mnt/user/appdata/unbound/ in the Config Path in the docker tab

    5. Paste in the unbound folder this files a-records.conf srv-records.conf forward-records.conf from https://github.com/MatthewVance/unbound-docker/tree/master/1.10.1 like suggested from debizaemon

    6. Create an folder unbound.conf.d in /mnt/user/appdata/unbound/

    7.  Create an txt file in unbound.conf.d with the settings from https://docs.pi-hole.net/guides/dns/unbound/

    8. rename it to pihole.conf after you save it

    9. Go to you Pihole then to settings/dns/costum1 IPv4 put in 127.0.0.1#5335 (dont forget to untick all the other DNS Upstreamservers)

    10. save it

     

    Then it should work (kind of), i still have time outs reaching the unraid ui. Please tell me how it worked out for you... A proper tutorial would be nice from the unbound (unraid) pros, because i still have issues (like i said) and have to stick to the conventional DNS Upstream Servers.

     

    What i noticed is that in the docker tab the container is still using port 53, instead of showing that it is using port 5335 (like put in the docker config) is this right?

  4. I have the issue with adguard + unbound that i cant access the unraid ui anymore i get the DNS_PROBE_POSSIBLE error, when i use the Unbound DNS IP.

     

    I set it up like this:

     

    Unbound.conf ip 127.0.0.1 port 5335 in the Docker template i put it in br0 network (shows in Adguard client list as unbound.br0) and the ip for it is 192.168.178.3 (thats what i use in the adguard DNS Settings). 

     

    After i save this settings the ui is not working anymore, but other sites are loading normal and ads also get blocked. So i guess unbound is doing its job. I also put a DNS Rebind in my router for unraid.net and the server ip but no luck to get it working.

     

    So any ideas what im doing wrong?

     

    Update: On Pi-Hole the Unraid Gui works but had an 

    Maximum number of concurrent DNS queries reached (max: 150) error

  5. Hello everyone!

     

    I´m new to Unraid and have installed the server (bought a key) with the help from tutorials (spaceinvader, among others). I had some problems with setting up a Windows 10 VM for gaming, with the famous Nvidia error 43 coming up. But after some research on the unraid forums and the internet i got it working after many trys using a command script at the startup of the array.

     

    As in the tutorial from Spaceinvader i used the VFIO-PCI Config (community application) to bind my Geforce 1070 graphics card and my nvme drive. That worked (till now) great and i could use the Win10 VM without problems. But after some shutdowns of the server the Unraid OS does not boot and hangs on the following screen (see picture)

     

    IMG_20201027_112806.thumb.jpg.fc7b2e46b08174f987a2bf3b8cd097b3.jpg

     

    So i tryed to boot in safe mode but had the same result (hangs). This problem happned after i used the Win10 VM for some time and shutdown the server.  I think it has to do with VFIO binding but dont know how to fix this, maybe the Unraid Pros have more knowledge then i !? Any help would be great thanks.

     

    Update: Fixed the problem by myself deleting the vfio binding in the Vfio CFG and Syslinux.cfg, if someone runs into the problem.

     

×
×
  • Create New...