Pihole dans docker sur QTS 5 bloque complètement la résolution de dns

Recherche :

Mot : Pseudo : Filtrer
Bas de page
Auteur	Sujet : Pihole dans docker sur QTS 5 bloque complètement la résolution de dns

anyb0dy

Bonjour,
Tout d'abord, j'espère poster dans la bonne catégorie.
J'ai installé pihole sur mon NAS QNAP TS431KX version d'OS : 5.0.0.2131. Je l'ai installé à travers un container docker en suivant le tutoriel de QNAP : https://www.qnap.com/en/qutube/video/ZvaQu5_QrJ4.
Je suis nouveau sur docker mais il me semble avoir suivi correctement le tutoriel en adaptant les IP etc.
Le problème, c'est que quand je veux accéder à une page web en utilisant le pihole comme DNS, impossible d'afficher la page, Firfox me dit "Impossible de se connecter au serveur à l’adresse XXX.". J'arrive bien à me connecter à l'interface d'admin du pihole quio a vu les requêtes passer et qui indique en avoir bloqué 13% maintenant. La console du container affiche :

Spoiler :

s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service _gravityonboot: stopping
s6-rc: info: service _gravityonboot successfully stopped
s6-rc: info: service lighttpd: stopping
Stopping lighttpd
s6-rc: info: service lighttpd successfully stopped
s6-rc: info: service pihole-FTL: stopping
Stopping pihole-FTL
s6-rc: info: service pihole-FTL successfully stopped
s6-rc: info: service _startup: stopping
s6-rc: info: service _startup successfully stopped
s6-rc: info: service _uid-gid-changer: stopping
s6-rc: info: service _uid-gid-changer successfully stopped
s6-rc: info: service cron: stopping
Stopping cron
s6-rc: info: service cron successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service cron: starting
s6-rc: info: service cron successfully started
s6-rc: info: service _uid-gid-changer: starting
s6-rc: info: service _uid-gid-changer successfully started
s6-rc: info: service _startup: starting
[i] Starting docker specific checks & setup for docker pihole/pihole
[i] Setting capabilities on pihole-FTL where possible
[i] Applying the following caps to pihole-FTL:
* CAP_CHOWN
* CAP_NET_BIND_SERVICE
* CAP_NET_RAW
[i] Ensuring basic configuration by re-running select functions from basic-install.sh

[i] Installing configs from /etc/.pihole...
[i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[✓] Installed /etc/dnsmasq.d/01-pihole.conf
[✓] Installed /etc/dnsmasq.d/06-rfc6761.conf

[i] Installing latest logrotate script...
[i] Existing logrotate file found. No changes made.
[i] Pre existing WEBPASSWORD found
[i] Added ENV to php:
"TZ" => "",
"PIHOLE_DOCKER_TAG" => "2022.09.2",
"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
"CORS_HOSTS" => "",
"VIRTUAL_HOST" => "0.0.0.0",
[i] Using IPv4 and IPv6
[i] Preexisting ad list /etc/pihole/adlists.list detected (exiting setup_blocklists early)
[i] Converting DNS1 to PIHOLE_DNS_
[i] Converting DNS2 to PIHOLE_DNS_
[i] Setting DNS servers based on PIHOLE_DNS_ variable
[i] Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0
[i] FTL binding to default interface: eth0
[i] Enabling Query Logging
[i] Testing lighttpd config: Syntax OK
[i] All config checks passed, cleared for startup ...
[i] Docker start setup complete

Current Pi-hole version is v5.12
Current AdminLTE version is v5.14.2
Current FTL version is v5.17
Container tag is: 2022.09.2

[i] pihole-FTL (no-daemon) will be started as pihole

s6-rc: info: service _startup successfully started
s6-rc: info: service pihole-FTL: starting
s6-rc: info: service pihole-FTL successfully started
s6-rc: info: service lighttpd: starting
s6-rc: info: service lighttpd successfully started
s6-rc: info: service _gravityonboot: starting
s6-rc: info: service _gravityonboot successfully started
Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[✗] DNS resolution is currently unavailable
[✗] DNS resolution is not available
Stopping pihole-FTL

(Désolé si c'est pas la bonne méthode pour partager ce genre de contenu, quelle est la bonne ?)
Est-ce que les 2 dernières lignes de la console expliquent le problème ?
Comment résoudre le problème ? J'ai trouvé un certain nombre de réponses différentes à ce problème sur le web, mais soit je n'arrive pas à les mettre en oeuvre soit elles ne fonctionnent pas.
Merci à ceux qui prendront le temps d'éclairer un noob.

Publicité

anyb0dy

Bonjour,
Le problème s'est résolu de lui-même sans action particulière de ma part, ni changement de configuration, ni reboot.
Les réponses que j'ai obtenu sur un autre forum sont ci-dessous :

I had the same problem and fixed it by updating resolve.conf. But unlike as suggested in some older posts, using a public dns ip, rather than loopback (127.0.0.1). Try doing this on the terminal:
vi /etc/resolve.conf
this will open the file with vi.
press "a" to add line and add nameserver 9.9.9.9 (or any other public DNS you prefer).
press escape and type wq and enter (to write to the file). Your resolv.conf file should just have nameserver 9.9.9.9 line. you can check this by typing more /etc/resolve.conf in the terminal.
Actually, ignore my post above. I found out that was not the case (I was trying multiple things at that time). Apparently, you need to change your /etc/resolve.dnsmasq file to add nameserver 127.0.0.1. I do not think you need to do anything with the /etc/resolve.conf file. If you check your /etc/dnsmasq.conf file you will see that it is set to read /etc/resolve.dnsmasq file by default. That's why you need to add loopback (127.0.0.1) to that file. Also, I think this file gets overwritten when you restart your NAS. So you may need to do it again. I am not 100% sure about that.

A prendre avec des pincettes vu que le participant lui-même semble se dédire.

FORUM HardWare.fr

Réseaux grand public / SoHo

Réseaux

Pihole dans docker sur QTS 5 bloque complètement la résolution de dns

Sujets relatifs
Échec de la connexion IEEE 802.3ad, bloqué à 115 mo/s sur D720+	[Pihole] Le réparer tous les 2 jours ou ne fonctionne pas.
Connexion VPN bloqué sur mon réseau	gmail, bloque la connexion imap si nouvelle IP
Orange Live Pro bloque mon routeur [RESOLU]	Accès à mon NAS depuis l'extérieur (bloqué à la maison)
[PiHole] Question vitesse	Carte réseau bloqué sur 10Mbit/s
Debit transfert bloqué a 11mo	Container docker et VPN
Plus de sujets relatifs à : Pihole dans docker sur QTS 5 bloque complètement la résolution de dns

Page générée en 0.058 secondes