simono41/docker-pihole-unbound
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Changing IPs

Browse source
This commit is contained in:
Chris Crowe 2019-03-21 22:33:53 -07:00
parent 2e3ec03edf
commit c438bbc7cf
4 changed files with 12 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -90,23 +90,23 @@ Test your configuration with dig
> __Note__: change the IP to your new Pi-Hole's IP > __Note__: change the IP to your new Pi-Hole's IP
```bash ```bash
dig google.com @192.168.1.248 dig google.com @192.168.1.5
# Expecting "status: NOERROR" # Expecting "status: NOERROR"
``` ```
You can also test for DNSSEC functionality: You can also test for DNSSEC functionality:
```bash ```bash
dig sigfail.verteiltesysteme.net @192.168.1.248 dig sigfail.verteiltesysteme.net @192.168.1.5
# Expecting "status: SERVFAIL" # Expecting "status: SERVFAIL"
dig sigok.verteiltesysteme.net @192.168.1.248 dig sigok.verteiltesysteme.net @192.168.1.5
# Expecting "status: NOERROR" # Expecting "status: NOERROR"
``` ```
### Serve it! ### Serve it!
If all looks good, configure your router/DHCP server to serve your new Pi-Hole IP address (`192.168.1.248`) to your clients. If all looks good, configure your router/DHCP server to serve your new Pi-Hole IP address (`192.168.1.5`) to your clients.
> Note: it may take some time for the current DHCP leases to renew and for clients to get the new DNS service info -- generally the default is 24 hours or less. > Note: it may take some time for the current DHCP leases to renew and for clients to get the new DNS service info -- generally the default is 24 hours or less.

11
docker-compose.yaml
View file

@ -14,10 +14,11 @@ services:
- 53/udp - 53/udp
# - 67/udp # Uncomment if you want to use Pi-Hole for DHCP # - 67/udp # Uncomment if you want to use Pi-Hole for DHCP
- 80/tcp - 80/tcp
- 22/tcp
environment: environment:
ServerIP: 192.168.1.248 ServerIP: 192.168.1.5
WEBPASSWORD: ${WEBPASSWORD} WEBPASSWORD: ${WEBPASSWORD}
DNS1: 192.168.1.249 DNS1: 192.168.1.6
DNS2: 192.168.1.13 DNS2: 192.168.1.13
volumes: volumes:
- /volume1/docker/pihole-unbound/pihole/volume:/etc/pihole:rw - /volume1/docker/pihole-unbound/pihole/volume:/etc/pihole:rw
@ -27,7 +28,7 @@ services:
- /volume1/docker/pihole-unbound/pihole/config/pihole-FTL.conf:/etc/pihole/pihole-FTL.conf:ro - /volume1/docker/pihole-unbound/pihole/config/pihole-FTL.conf:/etc/pihole/pihole-FTL.conf:ro
networks: networks:
home: home:
ipv4_address: 192.168.1.248 ipv4_address: 192.168.1.5
restart: always restart: always
unbound: unbound:
container_name: unbound container_name: unbound
@ -39,7 +40,7 @@ services:
- 53/udp - 53/udp
networks: networks:
home: home:
ipv4_address: 192.168.1.249 ipv4_address: 192.168.1.6
restart: always restart: always
networks: networks:
@ -51,4 +52,4 @@ networks:
config: config:
- subnet: 192.168.1.0/24 - subnet: 192.168.1.0/24
gateway: 192.168.1.1 gateway: 192.168.1.1
ip_range: 192.168.1.248/30 ip_range: 192.168.1.5/30 # 192.168.1.5 and 192.168.1.6

2
pihole/config/dnsmasq.conf
View file

@ -1,2 +1,2 @@
address=/gateway/192.168.1.1 address=/gateway/192.168.1.1
address=/pi-hole/pi-hole.local/192.168.1.248 address=/pi-hole/pi-hole.local/192.168.1.5

2
pihole/config/hosts
View file

@ -2,4 +2,4 @@
::1 pi-hole ::1 pi-hole
192.168.1.1 gateway 192.168.1.1 gateway
192.168.1.248 pi-hole 192.168.1.5 pi-hole