« Unbound - Pihole » : différence entre les versions

Aucun résumé des modifications
Aucun résumé des modifications
Ligne 1 : Ligne 1 :
== Unbound ==
== Unbound ==


Ligne 8 : Ligne 7 :
une conf pour les domaines en local dans /etc/unbound/unbound.conf.d/local.conf
une conf pour les domaines en local dans /etc/unbound/unbound.conf.d/local.conf
</pre>
</pre>


* https://www.azurs.net/carnet/2016/02/serveur-dns-local-sur-raspberry-pi-sous-arch-linux-arm/
* https://www.azurs.net/carnet/2016/02/serveur-dns-local-sur-raspberry-pi-sous-arch-linux-arm/
Ligne 37 : Ligne 35 :
         endscript
         endscript
}
}


#forcer logrotate
#forcer logrotate
sudo logrotate -f /etc/logrotate.d/unbound
sudo logrotate -f /etc/logrotate.d/unbound
</pre>
</pre>


* https://docs.pi-hole.net/guides/dns/unbound/
* https://docs.pi-hole.net/guides/dns/unbound/
Ligne 76 : Ligne 71 :
sudo wget -O /var/lib/unbound/root.hints https://www.internic.net/domain/named.root
sudo wget -O /var/lib/unbound/root.hints https://www.internic.net/domain/named.root
</pre>
</pre>


== pihole ==
== pihole ==
Ligne 123 : Ligne 117 :
pihole checkout : Checkout
pihole checkout : Checkout
</pre>
</pre>


=== Ports ===
=== Ports ===
<pre>
<pre>
We need ports 53, 80, and 4711. Port 80 is optional if you decide not to install the Web dashboard during installation.
We need ports 53, 80, and 4711. Port 80 is optional if you decide not to install the Web dashboard during installation.
Port 53(DNS) should be used by dnsmasq  
Port 53(DNS) should be used by dnsmasq  
TCP/UDP  
TCP/UDP  
If you happen to have another DNS server running, such as BIND, you will need to turn it off in order for Pi-hole to respond to DNS queries.
If you happen to have another DNS server running, such as BIND, you will need to turn it off in order for Pi-hole to respond to DNS queries.
Port 80(HTTP) should be used by lighttpd
Port 80(HTTP) should be used by lighttpd
TCP
TCP
If you have another Web server already running, such as Apache, Pi-hole's Web server will not work. You can either disable the other Web server or change the port on which lighttpd listens, which allows you keep both Web servers running.  
If you have another Web server already running, such as Apache, Pi-hole's Web server will not work. You can either disable the other Web server or change the port on which lighttpd listens, which allows you keep both Web servers running.  
Port 4711 should be used by pihole-FTL
Port 4711 should be used by pihole-FTL
TCP
TCP
FTL is our API engine and by default uses port 4711, but will increment if it's already in use by something else
FTL is our API engine and by default uses port 4711, but will increment if it's already in use by something else
FTL is our API engine and uses port 4711 on the localhost interface. This port should not be accessible from any other interface.  
FTL is our API engine and uses port 4711 on the localhost interface. This port should not be accessible from any other interface.  
Port 67(DHCP) should be used by DHCP
 
Port 67 (DHCP) should be used by DHCP
IPV4 UDP
IPV4 UDP
(option) pas de service DHCP
(option) pas de service DHCP
The DHCP server is an optional feature that requires additional ports.  
The DHCP server is an optional feature that requires additional ports.  
Port 547should be used by DHCPv6
Port 547should be used by DHCPv6
IPV6 UDP
IPV6 UDP
Ligne 171 : Ligne 169 :
pihole --wild -d facebook.com
pihole --wild -d facebook.com
</pre>
</pre>
[https://tutox.fr/2019/05/27/mettre-en-place-un-controle-parental-avec-pihole/ controle parental avec pihole]
[https://tutox.fr/2019/05/27/mettre-en-place-un-controle-parental-avec-pihole/ controle parental avec pihole]
 
 
 
 
 




[[Catégorie: Raspian]]
[[Catégorie: Raspian]]