I agree with @ronv42 unless you created a rule, firewalls do not block outbound traffic, mainly inbound. But DNS greatly affects outbound. How is your hub getting the IP stack, via DHCP? What DNS is the DHCP server giving out? Try adding Google's DNS as a secondary (188.8.131.52). Also can your computer resolve the address?
Try using a DHCP (better yet a DHCP reservation) to test and see if it can resolve with a distributed IP. If so work backwards from there to find the dif. Does your Hub have cloud access? Update and dashboards, is it just github or all internet traffic?
I set HE settings to static, thinking the DHCP settings in unifi needed to match.. I now have HE settings as DHCP, and Unifi set to DHCP overall, and static for the HE device. Everything is functioning properly
I tried many ways and decided to leverage the DHCP server in my Untangle router since each VLAN has it's own DHCP configuration. Those DHCP configs then points DNS to my Pi-hole which is on a "public VLAN core" and router rules setup for each VLAN to route to the Pi-hole for DNS.
I tried to have the Pi-hole listen on 0.0.0.0 and then created mutiple VLAN interfaces in the Pi and it was just not working. I am sure I missed something in that config when I was hand writing DNSmasq custom configurations.