There seems to be a loop resolving FQDN in LAN

The issue I am facing:
Ever since I've set a domain name on my router, I've noticed some strange activities.

Where once I usually get 200 queries per hour, it has now jumped to 2000 queries per hour.

pihole.log is full of the following records:

Mar 19 18:10:09 dnsmasq[3608298]: query[AAAA] localhost.local.home from 192.168.70.1
Mar 19 18:10:09 dnsmasq[3608298]: forwarded localhost.local.home to 192.168.70.1
Mar 19 18:10:09 dnsmasq[3608298]: query[AAAA] localhost.local.home from 192.168.70.1
Mar 19 18:10:09 dnsmasq[3608298]: cached localhost.local.home is (null)

As a consequence of this it has probably also led to this issue (which I've also raised):

Apart from the surge in number of queries, throwing off graph and historical data, and the the issue I've detailed above (#45481) pihole is working as expected.

And so while this issue is not critical, there is something not quite right.

Let me know if I'm doing something wrong or if there's a switch I should set. Thanks

Details about my system:

Router (192.168.70.1):

  • Custom Rom (FreshTomato router)
  • Provides DHCP
  • Hostname: router
  • Domain name: local.home
  • Forwards all DNS queries to Pihole

Environment:

  • Pihole OS: Ubuntu 20.04.2
  • Pihole: v5.2.4
  • Pihole web: v5.4
  • FTL: v5.7

What I have changed since installing Pi-hole:

  • Interface listening behavior: Listen on all interfaces, permit all origins
  • Never forward non-FQDNs: On
  • Use Conditional Forwarding: On
  • DNSSEC: Off

Conditional Forwarding setup:

  • LAN: 192.168.70.0/24
  • DHCP: 192.168.70.1
  • Local Domain: local.home

Conditional forwarding appears to be causing this loop.

1 Like

Correct. Turning off Conditional Forwarding has resolved this issue, as I discovered in the linked issue.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.