1
0
Fork 0
mirror of https://github.com/sujiba/pihole-unbound-hyperlocal.git synced 2025-07-10 05:45:14 +02:00

chore: clearer wording

This commit is contained in:
sujiba 2024-06-08 20:04:44 +02:00
parent eb0d03b960
commit f8cf091277

View file

@ -2,15 +2,18 @@
**IMPORTANT**: When using this Docker image, please report any bugs or suggestions to this repository directly. **IMPORTANT**: When using this Docker image, please report any bugs or suggestions to this repository directly.
### Overview ## Overview
- [Introduction](https://github.com/sujiba/pihole-unbound-hyperlocal#introduction)
- [Prerequisites](https://github.com/sujiba/pihole-unbound-hyperlocal#prerequisites) - [Pihole + Unbound + Hyperlocal](#pihole--unbound--hyperlocal)
- [First startup](https://github.com/sujiba/pihole-unbound-hyperlocal#first-startup) - [Overview](#overview)
- [Testing](https://github.com/sujiba/pihole-unbound-hyperlocal#testing) - [Introduction](#introduction)
- [Additional configuration](https://github.com/sujiba/pihole-unbound-hyperlocal#additional-configuration) - [Prerequisites](#prerequisites)
- [DNS Problems](https://github.com/sujiba/pihole-unbound-hyperlocal#dns-problems) - [First startup](#first-startup)
- [Blocklists](https://github.com/sujiba/pihole-unbound-hyperlocal#blocklists) - [resolv.conf](#resolvconf)
- [Acknowledgement](https://github.com/sujiba/pihole-unbound-hyperlocal#acknowledgement) - [Testing](#testing)
- [DNS problems](#dns-problems)
- [Blocklists](#blocklists)
- [Acknowledgement](#acknowledgement)
## Introduction ## Introduction
**Pi-hole**: **Pi-hole**:
@ -37,37 +40,50 @@ Start the container
``` ```
docker-compose up -d docker-compose up -d
``` ```
Check the logs
```
docker-compose logs -f
```
### resolv.conf
If you get the following error
```
pihole | Starting unbound
pihole | [✗] DNS resolution is currently unavailable
```
uncomment the following line in the docker-compose.yaml
```
#- ./resolv.conf:/etc/resolv.conf
```
and restart the container
```
docker-compose up -d --force-recreate
```
### Testing ### Testing
``` ```
docker exec -it pihole-unbound bash docker exec -it pihole-unbound bash
dig github.com @127.0.0.1 +short dig github.com @127.0.0.1 +short
dig sigfail.verteiltesysteme.net @127.0.0.1 | grep status dig sigfail.verteiltesysteme.net @127.0.0.1 | grep status
dig sigok.verteiltesysteme.net @127.0.0.1 | grep status dig sigok.verteiltesysteme.net @127.0.0.1 | grep status
``` ```
- First dig should show an IP address - First dig should show an IP address
- Second dig should show status: SERVFAIL - Second dig should show status: SERVFAIL
- Last dig should show status: NOERROR - Last dig should show status: NOERROR
#### resolv.conf
If you are having problems with the pihole deployment inside the container, uncomment the following line in the docker-compose.yaml
```
#- ./resolv.conf:/etc/resolv.conf
```
### Restart the container
```
docker-compose up -d --force-recreate
```
## DNS problems ## DNS problems
If you are running other docker containers on the same host and cannot use name resolution within those containers, you have to modify /etc/resolvconf.conf on your host system and uncomment the following: If you are running other docker containers on the same host and cannot use name resolution within these containers, you have to modify /etc/resolvconf.conf on your host system and uncomment the following:
``` ```
# If you run a local name server, you should uncomment the below line and # If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below. # configure your subscribers configuration files below.
name_servers=127.0.0.1 name_servers=127.0.0.1
``` ```
The following command writes the changes to resolv.conf: Write the changes to your resolv.conf:
``` ```
sudo resolvconf -u sudo resolvconf -u
``` ```