Install Pi-Hole in Docker: Update 01/18/19 - Adding Unbound, a Recursive DNS Server. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.Īnd i followed the guide from these forums: (If configured, the IP address of the host where unbound is installed would be an exception,)ĭurch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. If security is a concern, setting a second DNS address, VIA the extra arguments, may not be a good idea. As I understand it, this would be a (temporary ? ) pi-hole bypass. As the Docker author explains it, this is a backup DNS entry in the event that Pi-hole's DNSMasq "malfunctions". The second DNS, as an extra argument, doesn't make sense to me. Outside of those conditions, this is optional. dns=127.0.01 is required only when using pi-hole as a DCHP server and local resolution of local hostnames is required/desired. This is, currently, in the Pi-hole How-To. The only additional parameter that's absolutely required is -cap-add=NET_ADMIN, in the Docker's extra arguments line. If using this How-To with the latest Docker image : With a bit of hands on, every 4 to 6 months, the update issue can be dealt with, without "surprises". Moreover, users may not know that their setup doesn't work, until network Clients can't resolve hosts. (My opinion.) One can go from a working Docker to a dead Docker, "automatically". It is for this exact reason that I believe using Watchtower is a bad idea. With Watchtower and scheduled job with this script : Which turns in a loop and this in pihole.log : Using log file /var/log/pihole-FTL.log Alles anzeigen Listening on port 4711 for incoming IPv4 telnet connections Imported 0 queries from the long-term database Compiled 0 Regex filters and 0 whitelisted domains in 0.0 msec (0 errors) AUDITLISTFILE: Using /etc/pihole/auditlog.list REGEXLISTFILE: Using /etc/pihole/regex.list GRAVITYFILE: Using /etc/pihole/gravity.list BLACKLISTFILE: Using /etc/pihole/black.list WHITELISTFILE: Using /etc/pihole/whitelist.txt SOCKETFILE: Using /var/run/pihole/FTL.sock PORTFILE: Using /var/run/pihole-FTL.port DBIMPORT: Importing history from database BLOCKINGMODE: Null IPs for blocked domains IGNORE_LOCALHOST: Show queries from localhost MAXLOGAGE: Importing up to 24.0 hours of log data DBINTERVAL: saving to DB file every minute MAXDBDAYS: max age for stored queries is 365 days Starting config file parsing (/etc/pihole/nf) WARNING: Starting pihole-FTL as user root is not recommended
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |