• Hi guys,

    I have a pi-hole running in my network with also a IOT vlan. the IOT devices are using pihole as DNS server as expected. But i have an issue. The mDNS Avahi services seems like it doesn't work. I guess it is because all the dns traffic is handled by the pi-hole. (i followed the YT vid from Lawrence systems)

    What would be a good solution to have avahi working while my first dns server in the whole network is pi-hole?

    If pi-hole is not the problem, can someone explain why casting is not working?

    (my upstream dns is set to pfsense on pi-hole and the dns servers on pfsense are 1.1.1.1 8.8.8.8 and 9.9.9.9DHCP -> pi-hole -> pfsense -> 1.1.1.1/8.8.8.8/9.9.9.9)


  • @ACNiC said in avahi mdns with pihole and pfsense:

    If pi-hole is not the problem, can someone explain why casting is not working?

    Hi,

    because the Unbound + pfBlocker-devel is miles better than pi-hole and is included in pfSense

    +++edit:
    I always say that, if you can handle DNS in one place, if you use NGFW...... it makes sense


  • Hi @ACNiC - I've got a similar setup as yours with Pi-hole as the first DNS server and pfSense upstream. Avahi works just fine and I've never had any trouble with mDNS even with the IoT devices (such as Google Chromecasts, etc.) located on a different network segment than other devices.

    Couple questions:

    1. What exactly do you mean by "casting is not working"? Is is that you can't see / connect to e.g. Chromecasts from a device in a different network segment?

    2. Are your firewall rules setup properly to allow the necessary traffic to flow between device and IoT network so that casting can work?

    3. What options do you have checked under "Advanced DNS Settings" in Pi-hole?

    Hope this helps.