Query Log Reply: N/A no answer

The issue I am facing:
Sometimes I get a long time no dns resolution when using firefox and I have to refresh the tab multiple times to get a page loading. Also during page loads some domains can not be resolved and so there is css missing or some other stuff.

Details about my system:
Ubuntu 24.04
Pihole running in a docker container with a compose file.
I use 2 dns servers. 1. for all domains and the second one for specific local domains.
compose file:

# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:2024.07.0
    # For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
    ports:
      - "127.0.0.1:53:53/tcp"
      - "127.0.0.1:53:53/udp"
      #- "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "127.0.0.1:80:80/tcp"
    environment:
      TZ: 'Europe/Vienna'
      WEBPASSWORD: 'pihole'
      PIHOLE_DNS_: '193.110.81.0'
    # Volumes store your data between container upgrades
    volumes:
      - './etc-pihole:/etc/pihole'
      - './etc-dnsmasq.d:/etc/dnsmasq.d'
    #   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    # cap_add:
      # - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed
    restart: unless-stopped

I have a 09-custom.conf file for the dnsmasq.s that I mount that looks like this:

server=/domain.com/172.16.0.2
server=/service.consul/172.16.0.2
server=/node.consul/172.16.0.2
local-ttl=300
min-cache-ttl=60

to route the internal dns requests.

What I have changed since installing Pi-hole:
It behaves like this since I set it up.

Debug Log
(moderator edit: explicit debug log removed)

Edit: Was a firewall issue, nothing wrong with pihole.

For your own privacy and security, please do not post your full, unsanitised debug log.
We just ask for the token.

Your screenshot shows that Pi-hole has correctly forwarded DNS requests for accounts.google.com to dns0.eu.
N/A indicates that Pi-hole has not received a reply for that request, i.e. dns0.eu failed to provide an answer.

This would suggest that your chosen upstream is unavailable or unresponsive at times. It's also possible that unstable Internet connectivity could cause your issue.

Try switching to another upstream DNS server.
If your issue would cease, then it would be specific to dns0.eu.
If it doesn't, then your machine's connectivity may lag or drop at times.
If your Pi-hole machine is using a wifi connection to your router, make sure that wifi power saving is disabled.