Accès externe par DNS Jeedom et pihole

Discussions Générales
1

Hello,

Je me fais la main sur l’utilisation de pihole sur un raspi 4B sur mon réseau locale piloté par une Freebox pop. J’ai l’impression que j’ai un conflit entre le pihole et le fonctionnement des DNS Jeedom pour l’accès externe.
Spoiler : je suis débutant sur le sujet !
Le pihole est fonctionnel, j’ai paramétré la fonction DHCP sur la Freebox pour indiquer comme serveur DNS l’IP locale du raspi (fixé par bail dhcp statique), et cela semble fonctionner puisque je vois sur le dashboard du pihole qu’il voit du trafic et bloque certaines requêtes.
Mais, une fois ça en place je n’arrive plus à accéder à mon Jeedom depuis l’extérieur, en sachant que j’utilise les DNS Jeedom, avec le plugin OpenVPN installé, et tout ça fonctionne quand je reparamètre le serveur DNS sur la Freebox comme à l’origine.

Est-ce que je fais qqch mal ? Je pense que je maîtrise mal le principe du DNS et encore plus le fonctionnement de l’accès externe par DNS Jeedom…

2

Salut,

Ton rpi est en ip fixe ou en dhcp sur ton réseau ?
Tu ne peux pas mettre un autre DNS en dur sur la machine ?

3

Bonsoir
Ton dns local c’est bien ton pihole !!!

4

l’IP du raspi est attribuée par DHCP par la Freebox (bail statique donc fixe).
De quelle machine tu parles pour le DNS en dur ?

5

Bah oui c’est ce que je fais en paramétrant ma Freebox avec l’adresse du pihole comme serveur DNS.

6

De celle la. Mets un autre DNS sur le raspberry pour voir si c’est lui qui pose problème ou pas.

7

Tu veux dire dans la config de pihole, lui dire d’utiliser autre chose que les DNS google ou Opendns ?

8

A priori il n’y a pas de lien entre le serveur dns utilisé sur ton réseau (pihole) et l’accès distance jeedom; un peu abusivement appelé parfois « accès dns », ce qui est trompeur ici peut-être.

Le seul lien c’est que ton jeedom doit utiliser un serveur dns pour ses requêtes sortantes, y compris mais pas uniquement celles pour établir le vpn avec le proxy de jeedom.

Donc moi je vérifierais d’abord que ton jeedom arrive bien à effectuer des requêtes sortantes en utilisant pihole comme serveur dns.
Si tu changes la config dans ta box internet peut-être que celles-ci ne répond plus aux requêtes dns mais que ton jeedom n’a pas reçu l’info qu’il devait utiliser pihole? Du coup il est bloqué et rien en fonctionne, y compris le vpn

9

Effectivement je viens de retester et ce n’est pas que l’accès depuis l’extérieur, plusieurs plugins/équipements qui ont besoin d’accès vers l’extérieur qui ne fonctionnent plus : lgthinq2 (qui a besoin de se connecter au hub LG je pense), un script qui scanne Doctolib, les notifs JeedomConnect…

10

pour vérifier les serveurs dns actuellement utilisé par jeedom:

cat /etc/resolv.conf

tu peux faire ca via les outils système jeedom

un peu overkill mais as-tu déjà fait un simple reboot de jeedom après avoir changé la config serveur dns dans ta box? (il y a moyen de taper des lignes de commandes mais le reboot est plus simple :wink: )

11

Non en effet j’ai reboot la Freebox pour appliquer les nouveaux DNS mais pas l’atlas. Je vais tester.

12

Testé à l’instant, rien de mieux :frowning:
Je me demande si c’est lié à ça :

IMPORTANT

Pour que cela fonctionne il faut que votre box autorise une connexion sortante sur les ports 1194,1195,1196,1197,1198,1199,2000 et 2001 en UDP.

13

Je ne pense pas que la BOX filtre ces ports si tu ne l’a pas demandé de façon explicite.

Par contre que donne les logs openvpn ?

14 
0000|[2026-01-24 15:27:47] INFO  Lancement openvpn : sudo openvpn --config /tmp/jeedom/openvpn/openvpn_6.ovpn >> /var/www/html/core/class/../../log/openvpn_DNS_Jeedom  2>&1 &
0001|2026-01-24 15:27:47 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
0002|2026-01-24 15:27:47 --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
0003|2026-01-24 15:27:47 WARNING: file '/tmp/jeedom/openvpn/openvpn_auth_NTWCkgXD2498vIgiasSLrQIHH99dC9.conf' is group or others accessible
0004|2026-01-24 15:27:47 OpenVPN 2.5.1 aarch64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Aug 25 2025
0005|2026-01-24 15:27:47 library versions: OpenSSL 1.1.1w  11 Sep 2023, LZO 2.10
0006|2026-01-24 15:27:47 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0007|2026-01-24 15:27:47 TCP/UDP: Preserving recently used remote address: [AF_INET]212.27.38.252:1201
0008|2026-01-24 15:27:47 UDP link local: (not bound)
0009|2026-01-24 15:27:47 UDP link remote: [AF_INET]212.27.38.252:1201
0010|2026-01-24 15:28:48 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
0011|2026-01-24 15:28:48 TLS Error: TLS handshake failed
0012|2026-01-24 15:28:48 SIGUSR1[soft,tls-error] received, process restarting
0013|2026-01-24 15:28:53 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0014|2026-01-24 15:28:53 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0015|2026-01-24 15:28:53 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0016|2026-01-24 15:28:53 Could not determine IPv4/IPv6 protocol
0017|2026-01-24 15:28:53 SIGUSR1[soft,init_instance] received, process restarting
0018|2026-01-24 15:28:58 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0019|2026-01-24 15:28:58 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0020|2026-01-24 15:28:58 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0021|2026-01-24 15:28:58 Could not determine IPv4/IPv6 protocol
0022|2026-01-24 15:28:58 SIGUSR1[soft,init_instance] received, process restarting
0023|2026-01-24 15:29:03 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0024|2026-01-24 15:29:03 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0025|2026-01-24 15:29:03 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0026|2026-01-24 15:29:03 Could not determine IPv4/IPv6 protocol
0027|2026-01-24 15:29:03 SIGUSR1[soft,init_instance] received, process restarting
0028|2026-01-24 15:29:08 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0029|2026-01-24 15:29:08 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0030|2026-01-24 15:29:08 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0031|2026-01-24 15:29:08 Could not determine IPv4/IPv6 protocol
0032|2026-01-24 15:29:08 SIGUSR1[soft,init_instance] received, process restarting
0033|2026-01-24 15:29:13 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0034|2026-01-24 15:29:13 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0035|2026-01-24 15:29:13 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0036|2026-01-24 15:29:13 Could not determine IPv4/IPv6 protocol
0037|2026-01-24 15:29:13 SIGUSR1[soft,init_instance] received, process restarting
0038|2026-01-24 15:29:18 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0039|2026-01-24 15:29:18 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0040|2026-01-24 15:29:18 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0041|2026-01-24 15:29:18 Could not determine IPv4/IPv6 protocol
0042|2026-01-24 15:29:18 SIGUSR1[soft,init_instance] received, process restarting
0043|2026-01-24 15:29:23 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0044|2026-01-24 15:29:23 TCP/UDP: Preserving recently used remote address: [AF_INET]212.27.38.252:1201
0045|2026-01-24 15:29:23 UDP link local: (not bound)
0046|2026-01-24 15:29:23 UDP link remote: [AF_INET]212.27.38.252:1201
0047|2026-01-24 15:30:23 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
0048|2026-01-24 15:30:23 TLS Error: TLS handshake failed
0049|2026-01-24 15:30:23 SIGUSR1[soft,tls-error] received, process restarting
0050|2026-01-24 15:30:28 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0051|2026-01-24 15:30:28 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0052|2026-01-24 15:30:28 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0053|2026-01-24 15:30:28 Could not determine IPv4/IPv6 protocol
0054|2026-01-24 15:30:28 SIGUSR1[soft,init_instance] received, process restarting
0055|2026-01-24 15:30:33 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0056|2026-01-24 15:30:33 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0057|2026-01-24 15:30:33 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0058|2026-01-24 15:30:33 Could not determine IPv4/IPv6 protocol
0059|2026-01-24 15:30:33 SIGUSR1[soft,init_instance] received, process restarting
0060|2026-01-24 15:30:38 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0061|2026-01-24 15:30:38 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0062|2026-01-24 15:30:38 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0063|2026-01-24 15:30:38 Could not determine IPv4/IPv6 protocol
0064|2026-01-24 15:30:38 SIGUSR1[soft,init_instance] received, process restarting
0065|2026-01-24 15:30:43 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0066|2026-01-24 15:30:43 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0067|2026-01-24 15:30:43 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0068|2026-01-24 15:30:43 Could not determine IPv4/IPv6 protocol
0069|2026-01-24 15:30:43 SIGUSR1[soft,init_instance] received, process restarting
0070|2026-01-24 15:30:48 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0071|2026-01-24 15:30:48 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0072|2026-01-24 15:30:48 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0073|2026-01-24 15:30:48 Could not determine IPv4/IPv6 protocol
0074|2026-01-24 15:30:48 SIGUSR1[soft,init_instance] received, process restarting
0075|2026-01-24 15:30:53 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0076|2026-01-24 15:30:53 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0077|2026-01-24 15:30:53 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0078|2026-01-24 15:30:53 Could not determine IPv4/IPv6 protocol
0079|2026-01-24 15:30:53 SIGUSR1[soft,init_instance] received, process restarting
0080|2026-01-24 15:30:58 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0081|2026-01-24 15:30:58 TCP/UDP: Preserving recently used remote address: [AF_INET]212.27.38.252:1201
0082|2026-01-24 15:30:58 UDP link local: (not bound)
0083|2026-01-24 15:30:58 UDP link remote: [AF_INET]212.27.38.252:1201
0084|2026-01-24 15:31:58 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
0085|2026-01-24 15:31:58 TLS Error: TLS handshake failed
0086|2026-01-24 15:31:58 SIGUSR1[soft,tls-error] received, process restarting
0087|2026-01-24 15:32:03 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0088|2026-01-24 15:32:03 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0089|2026-01-24 15:32:03 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0090|2026-01-24 15:32:03 Could not determine IPv4/IPv6 protocol
0091|2026-01-24 15:32:03 SIGUSR1[soft,init_instance] received, process restarting
0092|2026-01-24 15:32:08 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0093|2026-01-24 15:32:08 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0094|2026-01-24 15:32:08 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0095|2026-01-24 15:32:08 Could not determine IPv4/IPv6 protocol
0096|2026-01-24 15:32:08 SIGUSR1[soft,init_instance] received, process restarting
0097|2026-01-24 15:32:13 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0098|2026-01-24 15:32:13 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0099|2026-01-24 15:32:13 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0100|2026-01-24 15:32:13 Could not determine IPv4/IPv6 protocol
0101|2026-01-24 15:32:13 SIGUSR1[soft,init_instance] received, process restarting
0102|2026-01-24 15:32:18 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0103|2026-01-24 15:32:18 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0104|2026-01-24 15:32:19 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0105|2026-01-24 15:32:19 Could not determine IPv4/IPv6 protocol
0106|2026-01-24 15:32:19 SIGUSR1[soft,init_instance] received, process restarting
0107|2026-01-24 15:32:24 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0108|2026-01-24 15:32:24 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0109|2026-01-24 15:32:24 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0110|2026-01-24 15:32:24 Could not determine IPv4/IPv6 protocol
0111|2026-01-24 15:32:24 SIGUSR1[soft,init_instance] received, process restarting
0112|2026-01-24 15:32:29 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0113|2026-01-24 15:32:29 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0114|2026-01-24 15:32:29 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0115|2026-01-24 15:32:29 Could not determine IPv4/IPv6 protocol
0116|2026-01-24 15:32:29 SIGUSR1[soft,init_instance] received, process restarting
0117|2026-01-24 15:32:34 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0118|2026-01-24 15:32:34 TCP/UDP: Preserving recently used remote address: [AF_INET]212.27.38.252:1201
0119|2026-01-24 15:32:34 UDP link local: (not bound)
0120|2026-01-24 15:32:34 UDP link remote: [AF_INET]212.27.38.252:1201
0121|2026-01-24 15:33:34 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
0122|2026-01-24 15:33:34 TLS Error: TLS handshake failed
0123|2026-01-24 15:33:34 SIGUSR1[soft,tls-error] received, process restarting
0124|2026-01-24 15:33:39 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0125|2026-01-24 15:33:40 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0126|2026-01-24 15:33:40 RESOLVE: Cannot resolve host address: vpn3.host.eu.jeedom.link:1201 (Name or service not known)
0127|2026-01-24 15:33:40 Could not determine IPv4/IPv6 protocol
0128|2026-01-24 15:33:40 SIGUSR1[soft,init_instance] received, process restarting
0129|2026-01-24 15:33:45 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0130|2026-01-24 15:33:45 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0131|2026-01-24 15:33:45 RESOLVE: Cannot resolve host address: vpn1.host.eu.jeedom.link:1201 (Name or service not known)
0132|2026-01-24 15:33:45 Could not determine IPv4/IPv6 protocol
0133|2026-01-24 15:33:45 SIGUSR1[soft,init_instance] received, process restarting
0134|2026-01-24 15:33:50 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0135|2026-01-24 15:34:00 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0136|2026-01-24 15:34:05 RESOLVE: Cannot resolve host address: vpn2.host.eu.jeedom.link:1201 (Name or service not known)
0137|2026-01-24 15:34:05 Could not determine IPv4/IPv6 protocol
0138|2026-01-24 15:34:05 SIGUSR1[soft,init_instance] received, process restarting
0139|2026-01-24 15:34:10 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0140|2026-01-24 15:34:10 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0141|2026-01-24 15:34:10 RESOLVE: Cannot resolve host address: vpn5.host.eu.jeedom.link:1201 (Name or service not known)
0142|2026-01-24 15:34:10 Could not determine IPv4/IPv6 protocol
0143|2026-01-24 15:34:10 SIGUSR1[soft,init_instance] received, process restarting
0144|2026-01-24 15:34:15 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0145|2026-01-24 15:34:15 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0146|2026-01-24 15:34:15 RESOLVE: Cannot resolve host address: vpn6.host.eu.jeedom.link:1201 (Name or service not known)
0147|2026-01-24 15:34:15 Could not determine IPv4/IPv6 protocol
0148|2026-01-24 15:34:15 SIGUSR1[soft,init_instance] received, process restarting
0149|2026-01-24 15:34:20 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0150|2026-01-24 15:34:20 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0151|2026-01-24 15:34:20 RESOLVE: Cannot resolve host address: vpn4.host.eu.jeedom.link:1201 (Name or service not known)
0152|2026-01-24 15:34:20 Could not determine IPv4/IPv6 protocol
0153|2026-01-24 15:34:20 SIGUSR1[soft,init_instance] received, process restarting
0154|2026-01-24 15:34:25 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0155|2026-01-24 15:34:25 RESOLVE: Cannot resolve host address: vpn7.host.eu.jeedom.link:1201 (Name or service not known)
0156|2026-01-24 15:34:25 RESOLVE: Cannot resolve host address: vpn7.host.eu.jeedom.link:1201 (Name or service not known)
0157|2026-01-24 15:34:25 Could not determine IPv4/IPv6 protocol
0158|2026-01-24 15:34:25 SIGUSR1[soft,init_instance] received, process restarting
0159|2026-01-24 15:34:30 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
0160|2026-01-24 15:34:30 TCP/UDP: Preserving recently used remote address: [AF_INET]51.159.177.9:1201
0161|2026-01-24 15:34:30 UDP link local: (not bound)
0162|2026-01-24 15:34:30 UDP link remote: [AF_INET]51.159.177.9:1201
0163|2026-01-24 15:34:32 VERIFY OK: depth=1, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=jeedom.com CA, name=jeedom, emailAddress=postmaster@jeedom.com
0164|2026-01-24 15:34:32 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
0165|2026-01-24 15:34:32 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1542', remote='link-mtu 1342'
0166|2026-01-24 15:34:32 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1300'
0167|2026-01-24 15:34:32 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 1024 bit RSA
0168|2026-01-24 15:34:32 [server] Peer Connection Initiated with [AF_INET]51.159.177.9:1201
0169|2026-01-24 15:34:32 Data Channel: using negotiated cipher 'AES-256-GCM'
0170|2026-01-24 15:34:32 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
0171|2026-01-24 15:34:32 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
0172|2026-01-24 15:34:32 TUN/TAP device tun0 opened
0173|2026-01-24 15:34:32 net_iface_mtu_set: mtu 1500 for tun0
0174|2026-01-24 15:34:32 net_iface_up: set tun0 up
0175|2026-01-24 15:34:32 net_addr_ptp_v4_add: 10.16.21.110 peer 10.16.21.109 dev tun0
0176|2026-01-24 15
15

Dans le log on voit qu’il n’arrive pas a faire de résolution dns.

Fait ce qu’a suggéré Mips plus haut

cat /etc/resolv.conf

Et colle le résultat ici

16

Salut,

Tu n’aurais pas activé du filtrage sur les connexions VPN dans ton pihole ?

Essai rapidement de désactiver temporairement l’ensemble des protections pendant 10mn (de mémoire il y a un lien à gauche dans le menu). Ça permettra de vérifier que ce n’est pas le filtrage sur un service qui pose problème

17

Même avec le filtrage désactivé sur pihole rien ne passe.
La commande proposée par @Mips donne

# Generated by NetworkManager
nameserver 192.168.1.10

C’est bien l’IP du raspi sur lequel pihole est installé.

18

Jeedom est sur un réseau différent de 192.168.1.0/24 ?

Si c’est le cas, il y a un truc assez spécifique pour que pihole accepte de résoudre pour des IP qui ne sont pas dans son son propre réseau

19

Ce qui serait bien c’est de voir si il ne résoud plus rien ou si c’est juste les openVPN de jeedom qui sont bloqués.

Si tu fais :

host www.google.fr

Ca te renvoi quoi ?

20

Non, tous mes équipements sont sur 192.168.1.x , attribués par DHCP de la freebox, en bail statique pour la plupart.

Screenshot_20260124-194131
Screenshot_20260124-1941311079×1350 128 KB