Pi-hole v6 "DNS server failure"

[ErikDB]

I did some more googling, and was able to find the VM, of which I have no recollection of making. It also had an IP address in a range for which I don't have a network...

I was able to destroy it. Now everything seems to work!

erik@MinipcLG2:~$ virsh net-list
 Name      State    Autostart   Persistent
--------------------------------------------
 default   active   yes         yes
erik@MinipcLG2:~$ virsh net-destroy default
Network default destroyed

erik@MinipcLG2:~$ virsh net-list
 Name   State   Autostart   Persistent
----------------------------------------

erik@MinipcLG2:~$ virsh net-undefine default
Network default has been undefined

erik@MinipcLG2:~$ virsh net-list
 Name   State   Autostart   Persistent
----------------------------------------

erik@MinipcLG2:~$ sudo reboot

[Roddy_Ruggabear]

I have a port conflict on 443 while trying to run Pihole on a Synology NAS via Docker. I tried editing the pihole.toml file to add/substitute 4443os but this did not help.

Hosting on the NAS has worked in the past with previous Pihole versions and it did work with v6 for a bit until I tried to upgrade again to the latest. I did try to kill the ngninx process on 443 that appears to conflict but it not die (and rebooting the NAS didn't help).

ERROR: for pihole  Cannot start service pihole: driver failed programming external connectivity on endpoint pihole (b4d30acdbe0c1b172b990dd19b72bbc782d6708a539b9ac853614d418329b0f7): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use

$ sudo netstat -ltnp | grep 443
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      9595/nginx: master  
tcp6       0      0 :::443                  :::*                    LISTEN      9595/nginx: master  

Previous docker-compose.yaml files had a number of network settings (for pihole_network, ServerIP) that the latest v6 file does not have. How would I set the IP address for the pihole in v6 (the NAS is on ...0.4 but pihole had been run on ...0.199?)

I do believe this will work (it already has) but there are some hurdles yet.

[nero355]

Please read Upgrading from v5.x - Pi-hole documentation and adjust where needed

[Roddy_Ruggabear]

Thanks for the reply - below is the compose file that worked for me. A few things that gave me trouble:

• Use version:2 of docker-compose.yaml if on older docker engine (I'm on DSM 6, Docker 18.09). And adjust IPAM config (ip_range is not supported)
• Use ovs_eth0 if OpenVSwitch is enabled (use ovs-vsctl -V to check on NAS)
• There's no need to forward ports, but they should be specified.
• Update the environment variables to the V6 versions (eg. WEBPASSWORD -> FTLCONF_webserver_api_password).

This guide is mostly right but doesn't have the V6 variables and I didn't notice the ovs_eth0 note.

version: '2'

services:
  pihole:
    image: pihole/pihole:latest
    container_name: pihole
    environment:
      TZ: 'America/Toronto'
      FTLCONF_webserver_api_password: 'dmh'
    volumes:
      - './etc-pihole:/etc/pihole'
    cap_add:
      - NET_ADMIN
    restart: unless-stopped
    hostname: pihole
    domainname: hhnas.local  
    dns:
      - 127.0.0.1
      - 8.8.8.8
    ports:
      - 443/tcp
      - 53/tcp
      - 53/udp
      - 67/udp
      - 80/tcp
    networks:
      macvlan_network:
        ipv4_address: 192.168.0.199

networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ovs_eth0
    ipam:
      config:
        - subnet: 192.168.0.0/24
          gateway: 192.168.0.1

[rdwebdesign]

@Roddy_Ruggabear

There's no need to forward ports, but they should be specified.

Port declaration is irrelevant and it will be ignored when you use macvlan network mode.

[Roddy_Ruggabear]

Thanks, I wasn't sure actually.