1/10/2024 0 Comments Gns3 docker unraid![]() ![]() So i tested unbound and i figured out that it is not using my nf file in the dir! Dont know why it is doing this. 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. In my own case, it solves DNS queries and is indeed listening my pihole request on port 5335. To me, it sounds like a false positive and refers to the out port for DNS request. 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. I'll add that you might be concerned about logs errors "due" to poor ressources for Unbound. 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? 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. Please tell me how it worked out for you. Then it should work (kind of), i still have time outs reaching the unraid ui. 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) Create an txt file in with the settings from Ĩ. Create an folder in /mnt/user/appdata/unbound/ħ. Paste in the unbound folder this files nf nf nf from like suggested from debizaemonĦ. Paste the path /mnt/user/appdata/unbound/ in the Config Path in the docker tabĥ. create an folder /mnt/user/appdata/unbound/Ĥ. connection timed out no servers could be reachedģ. Log files show the belowĬould 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. I've also noticed that only the nf file is present in the appdata unbound folder. I get this also as soon as I specify the appdata directory for config files. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound-checkconf unbound fatal error: Could not read config file: /opt/unbound/etc/unbound/nf. Any thoughts on how to resolve this? I'm hoping that it should be straight forward having share access to the unbound config files to modify them. ![]() Even after doing that the container will not start and throws a critical error listed below. However I'm unable to edit them unless I go in to the terminal and change the permissions. When I put in for instance host Path: /user/appdata/unbound which maps to Container Path: /opt/unbound/etc/unbound/. Building the container I see their is an option to mount the config to a share/volume. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |