NO, it's not normal
edit 28/01/2019 : YES it's normal , sorry for previous misinformation.
I do not see in your screen captures variable DNS1 and DNS2 like I post in my screen capture.
Do you post a new screen capture?
NO, it's not normal
edit 28/01/2019 : YES it's normal , sorry for previous misinformation.
I do not see in your screen captures variable DNS1 and DNS2 like I post in my screen capture.
Do you post a new screen capture?
Now I just want to make sure whether it is normal to have the "Misconfigured DNS in /etc/resolv.conf" warnings in Pi-hole's logs?
There's one error that jumps out Macvlan subnet setting 192.168.224.0/27 that should be 192.168.224.0/24
Alles anzeigenNO, it's not normal
I do not see in your screen captures variable DNS1 and DNS2 like I post in my screen capture.
Do you post a new screen capture?
Hi raulfg3,
It seems to me that the DNS1 and DNS2 in your screen capture are just "Environment variables" which are classified as optional from the official Pi-hole docker readme, and they are also not specified in the How-to guide and so I decided to skip them. Nevertheless, I also tried to put them but still getting the same error.
The --dns=127.0.0.1 that we have been discussing is in the "Extra arguments" section which is classified as a recommended settings according to the official Pi-hole docker readme, or a warning of "Misconfigured DNS in /etc/resolv.conf" may appear.
Thanks.
There's one error that jumps out Macvlan subnet setting 192.168.224.0/27 that should be 192.168.224.0/24
Hi geaves,
No, the size of my local subnet is intentionally decreased to match with my needs (as I don't have so many devices at home and so I limit the size of my LAN to /27). Therefore, the usable IP address on the LAN is 192.168.224.1-192.168.224.30, /27 is definitely a correct setting (same as what is defined in my router).
Thanks.
No, the size of my local subnet is intentionally decreased to match with my needs (as I don't have so many devices at home and so I limit the size of my LAN to /27).
Ok, I don't have many devices but leaving the defaults are usually a better option, but it's a long time since I've messed around with subnets. If your setting is /27 for the Macvlan I take it your subnet mask in your dhcp is 255.255.255.224
Ok, I don't have many devices but leaving the defaults are usually a better option, but it's a long time since I've messed around with subnets. If your setting is /27 for the Macvlan I take it your subnet mask in your dhcp is 255.255.255.224
Yes, correct, the subnet mask in my subnet is 255.255.255.224. I just wonder how the logs found "127.0.0.11" as I am pretty sure I didn't configure it anywhere in my OMV...
I just wonder how the logs found "127.0.0.11" as I am pretty sure I didn't configure it anywhere in my OMV...
The resolv.conf is dynamically generated so you can't edit it, there must be something else within your networking. I think that the .11 is dockers dns but I couldn't be sure.
The resolv.conf is dynamically generated so you can't edit it, there must be something else within your networking. I think that the .11 is dockers dns but I couldn't be sure.
Thanks for the info... that's why I really couldn't locate it. The worst thing is that in the official Pi-hole readme, it just mentioned about this "Misconfigured DNS in /etc/resolv.conf" warning may appear but never explain what will go wrong. I will just leave it if Pi-hole can function 100% as normal with this warning.
I am a networking guy and just new to OMV, hopefully can learn more from the folks here.
Thanks.
Hi raulfg3,
It seems to me that the DNS1 and DNS2 in your screen capture are just "Environment variables" which are classified as optional from the official Pi-hole docker readme, and they are also not specified in the How-to guide and so I decided to skip them. Nevertheless, I also tried to put them but still getting the same error.
The --dns=127.0.0.1 that we have been discussing is in the "Extra arguments" section which is classified as a recommended settings according to the official Pi-hole docker readme, or a warning of "Misconfigured DNS in /etc/resolv.conf" may appear.
Thanks.
use DNS1 variable and DNS2 variable is the same that use --dns= in extra arguments, the only diference is that variable way works for me and extra arguments no, so , do what you want.
Yep. I am also running unbound and pi-hole on my rockpro64 as a secondary dns. The only difference is mac mini is the dhcp server.
I am struggling for months how to make pihole working with rockpro64 I even updated to the the latest change in the guide
[How To] Install Pi-Hole in Docker: Update 01/18/19 - Adding Unbound, a Recursive DNS Server.
but I always get this in the log
:: Testing pihole-FTL DNS: FTL started!
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Docker start setup complete
[✗] DNS resolution is currently unavailable
I must say for the time being I am using my raspberry in the meantime just for the pihole function (on an other IP) without any issue.
So just wondering, what is the trick involved to have it working on the rockpro64?
127.0.0.11 is the Docker DNS resolver , very useful to use in letsencrypt docker to resolve other docker names like transmission, mldonke, radar, etc... in reverse proxy setup
use DNS1 variable and DNS2 variable is the same that use --dns= in extra arguments, the only diference is that variable way works for me and extra arguments no, so , do what you want.
Just tried again with variables DNS1 and DNS2:
But getting the same warning messages as per what I have mentioned before:
While leaving all other settings the same as the How-to:
Do you have any idea about what is going wrong?
Thanks.
Sorry, sorry, sorry, after days saying that is not normal, I see that I have the same lines in pi-hole logs.
my log is:
s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying...
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing...
stty: 'standard input': Inappropriate ioctl for device
::: Starting docker specific setup for docker pihole/pihole
WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11)
nameserver 127.0.0.11
options ndots:0
stty: 'standard input': Inappropriate ioctl for device
[i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u1
[i] Installing configs from /etc/.pihole...
[i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[i] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf...[K [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
Setting password: xxxx
+ pihole -a -p xxxx xxxx
[✓] New password set
Using custom DNS servers: 127.0.0.1 & 8.8.4.4
DNSMasq binding to custom interface: enp0s25
Added ENV to php:
Alles anzeigen
so YES, are normal, and sorry for days of confusing for my side.
but please post a screen capture like this to see if DNS are well configured:
OK, all is good.
and sorry again for the misinformation.
OK, all is good.
and sorry again for the misinformation.
No problem, actually really thanks a lot for keep trouble shooting with me.
what is the trick involved to have it working on the rockpro64?
My rockpro64 is running Ubuntu 18 if it makes a difference.
Hello,
I take advantage of this post to discuss my problem that I meet with my Pihole since the update me auto of my docker, it worked well before the update in 4.X
Now I have a problem with The FTL service is offline!
I looked in the log and it seems to have a problem with the DNS service that no longer runs. (I think in the docker)
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying...
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing...
stty: 'standard input': Inappropriate ioctl for device
::: Starting docker specific setup for docker pihole/pihole
WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11)
search workgroupe
nameserver 127.0.0.11
options ndots:0
stty: 'standard input': Inappropriate ioctl for device
[i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u1
[i] Installing configs from /etc/.pihole...
[i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[i] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf...[K [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Setting password: XXXXX
+ pihole -a -p XXXXX XXXXX
[✓] New password set
Using default DNS servers: 8.8.8.8 & 8.8.4.4
DNSMasq binding to default interface: eth0
Added ENV to php:
"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
"ServerIP" => "192.168.1.252",
"VIRTUAL_HOST" => "192.168.1.252",
Using IPv4 and IPv6
::: setup_blocklists now setting default blocklists up:
::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot
::: Blocklists (/etc/pihole/adlists.list) now set to:
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt
::: Testing pihole-FTL DNS: FTL started!
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Docker start setup complete
[i] Pi-hole blocking is enabled
[i] Neutrino emissions detected...
[K [✓] Pulling blocklist source list into range
[i] Target: raw.githubusercontent.com (hosts)
[i] Status: Pending...[K [✓] Status: Retrieval successful
[i] Target: mirror1.malwaredomains.com (justdomains)
[i] Status: Pending...[K [✓] Status: Retrieval successful
[i] Target: sysctl.org (hosts)
[i] Status: Pending...[K [✓] Status: Retrieval successful
[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
[i] Status: Pending...[K [✓] Status: Retrieval successful
[i] Target: s3.amazonaws.com (simple_tracking.txt)
[i] Status: Pending...[K [✓] Status: Retrieval successful
[i] Target: s3.amazonaws.com (simple_ad.txt)
[i] Status: Pending...[K [✓] Status: Retrieval successful
[i] Target: hosts-file.net (ad_servers.txt)
[i] Status: Pending...[K [✓] Status: Retrieval successful
[i] Consolidating blocklists...[K [✓] Consolidating blocklists
[i] Extracting domains from blocklists...[K [✓] Extracting domains from blocklists
[i] Number of domains being pulled in by gravity: 135410
[i] Removing duplicate domains...[K [✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 112780
[i] Nothing to whitelist!
[i] Number of regex filters: 0
[i] Parsing domains into hosts format...[K [✓] Parsing domains into hosts format
[i] Cleaning up stray matter...[K [✓] Cleaning up stray matter
[✗] DNS service is NOT running
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
[cont-init.d] 20-start.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting pihole-FTL (no-daemon)
Starting lighttpd
Starting crond
[services.d] done.
Stopping pihole-FTL
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Starting pihole-FTL (no-daemon)
Stopping pihole-FTL
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Starting pihole-FTL (no-daemon)
Stopping pihole-FTL
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Starting pihole-FTL (no-daemon)
Stopping pihole-FTL
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Alles anzeigen
Do you have any idea to solve this error ?
I redid an installation from the image and I still have the same problem.
how do you update your docker?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!