![]() 5.6 - #2 by DL6ER.Īnd likely unrelated to your problem, note that your other DHCP server distributes another. This may be a bit of a far call (as the error messages involved do not match), but since you are dealing with a fresh install, you may unintentionally have corrupted your database by running pihole -g -r - see Error: no such table: avity - Pi-hole v. Yet your debug log shows some database related errors about missing tables in Pi-hole's gravity database. However, you should then also see a corresponding RATE_LIMIT message in Pi-hole's diagnosis view - and your debug log doesn't include such a message. A debug log shows only a fraction of Pi-hole's log, but almost all contained queries originate from a. This would often be the case if a router had been configured to use Pi-hole as its upstream DNS server (as opposed to distributing it as local DNS server via DHCP). If a client would be expected to exceed the default 1,000 queries per minute, you may adjust that rate limit via nf. That observation - along with REFUSED log entries - would suggest that a client has exceeded Pi-hole's rate limit. When it happens, DNS resolution is down for maybe 2-5min, then comes back again for no apparent reason. Also, apps with existing connections keep working fine so I'm quite convinced it's not a connectivity issue. However I don't think dnsmasq caches connection errors, and it wouldn't explain why the resolution failure sometimes lasts 1-2min and sometimes lasts for 5min. ![]() Eventually the negative-cache times out and behaviour returns to normal.Pihole/dnsmasq caches this failure, and continues to return REFUSED for a period of time even once the upstream network issue has cleared.Pihole/dnsmasq queries all its upstream, finds it can't reach any of them, and returns REFUSED to the client.A client requests DNS resolution during this loss of connectivity.A very brief transient network failure occurs.The only scenario I can come up with is something like: The internet connection is quite stable, and this pihole hasn't been rebooted or anything recently. I can't think of any reason why this would happen, particularly only on this pihole installation. Changing the new pihole to use OpenDNS instead has not fixed the problem. At first I thought it was a genuine upstream problem, because the old install uses OpenDNS and I'm trying Cloudflare on the new one. The old pihole installation has never exhibited this behaviour. Jan 12 17:21:40 dnsmasq: config error is REFUSED (EDE: network error) The corresponding log entry is pihole.log is Jan 12 17:21:40 dnsmasq: query from 192.168.1.70 Set reply to REFUSED (8) in src/dnsmasq_interface.c:2071Īll the failures follow this same format. **** got cache reply: error is REFUSED (nowhere to forward to) (ID 6726, src/dnsmasq/rfc1035.c:1110) Setting DEBUG_QUERIES=true I can see the following in pihole-FTL.log: **** new UDP IPv4 query query "" from eth0/192.168.1.70#37148 (ID 6726, FTL 29316, src/dnsmasq/forward.c:1601) As such, I've enabled v4 and v6 upstream resolvers in Pihole. ![]() My ISP delegates a prefix to the router and clients autoconfigure themselves. My internet connection has native v4 and v6 support. Both are attached by onboard ethernet and I have no reason to doubt their reliability. The old pihole install is an RPi 4 running Raspbian, the new one is a Radxa RockPi S running Ubuntu 20.04 with Radxa's custom 4.4 kernel for the hardware. I would eventually like to make this new pihole the sole DHCP server and DNS resolver on the network, and then later add a second similarly-configured pihole for high availability. This setup has allowed me to test enabling pihole filtering for devices on the network without making it a single point of failure. It's somewhat messy, but my network has a few DHCP servers running on the same segment with non-overlapping IP pools: the Unifi USG3 gateway, the old pihole box, and the new pihole box. The config should be quite similar, and I copied the config from the old one using Teleporter, checking all the checkboxes during import. I built this pihole box intending it to replace an existing proof-of-concept install on my network. ![]() I've tried capturing debug info but wasn't able to catch it in the middle of the latest failure. However, using dig to query pihole's upstream servers directly (Cloudflare 1.1.1.1) works just fine, so this isn't an internet connection dropout. Using dig on the pihole I get the same results (querying its own dnsmasq instance). Failures are instant, and using nslookup I can confirm that Pihole is returning a "Refused" response. Chome on my Windows workstation will occassionally stop working due to DNS failures. I'm experiencing unusual behaviour on a new installation of Pihole.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |