Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider NOT rate-limiting queries from the local router #5586

Open
mgogulapati opened this issue Feb 22, 2024 · 5 comments
Open

Consider NOT rate-limiting queries from the local router #5586

mgogulapati opened this issue Feb 22, 2024 · 5 comments
Labels

Comments

@mgogulapati
Copy link

Versions

Pi-hole version is v5.17.3 (Latest: v5.17.3)
web version is v5.21 (Latest: v5.21)
FTL version is v5.25.1 (Latest: v5.25.1)

Platform

  • OS and version: Raspbian GNU/Linux 11 (bullseye)
  • Platform: Raspberry Pi 400 Rev 1.1

Configuration

_ Pi-hole's IP address is configured as the ONLY DNS server in the router/gateway_

Expected behavior

DNS quires to pi-hole from the local DNS server of the network need not be considered for rate limiting.

Actual behavior / bug

_While considering rate-limiting per client basis on the local networks, the local router/gateway is also being rate-limited, when it is forwarding all received DNS queries to the pi-hole for resolution.
Consider NOT rate-limiting the gateway's DNS queries _

Steps to reproduce

Steps to reproduce the behavior:

  1. Install pi-hole with static local IP address (192.168.192.3)
  2. Configure pi-hole as the DNS server on the router (192.168.192.1)
  3. Allow the local clients to generate requests (There are about 40+ clients on my network)
  4. The problem happens, when there is sudden surge of the network traffic.

Debug Token

Screenshots

Screenshot-1

Additional context

Add any other context about the problem here.

Copy link

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.

@github-actions github-actions bot added the stale label Mar 23, 2024
@mgogulapati
Copy link
Author

I have about 40 devices in my home network and i see this message almost everyday. Please let me know, if you need any other information related to this.

@github-actions github-actions bot removed the stale label Mar 28, 2024
@PromoFaux
Copy link
Member

PromoFaux commented Apr 1, 2024

Is it not possible in your router to set the DNS server for the clients to Pi-hole via DHCP?

That way all clients would directly query the Pi-hole rather than the router, which then forwards the requests to the Pi-hole.

Rate limiting is also configurable: https://docs.pi-hole.net/ftldns/configfile/#rate_limit, but the better fix would be to adjust your network configuration if possible

@mgogulapati
Copy link
Author

@PromoFaux, Thank you for responding.

Is it not possible in your router to set the DNS server for the clients to Pi-hole via DHCP?

Even though the Netgear (AX5200) router is configured to use the Pi-hole as the DNS server, it announces itself as the DNS server for the local hosts. I have included some additional information at the end.

Related to the rate-limiting configuration, the default configuration is set globally for all local clients. That is the reason, I am recommending removing the restriction on the local router / DNS server.

Local client (Win 11) information

C:\WINDOWS\system32>
C:\WINDOWS\system32> ipconfig /all

** Deleted information **

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix: search.charter.net
Description: Intel(R) Dual Band Wireless-AC 3165
Physical Address: XX-XX-XX-XX-B7-AF
DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
IPv6 Address: 2603:9008:1b00: 34cc: f239: fccd: 63fa: 931f(Preferred)
Temporary IPv6 Address: 2603:9008:1b00: 34cc: e976:18eb:e592:fff1(Preferred)
Link-local IPv6 Address: fe80 :: 93df: 18b1: db52: 2eb4%3(Preferred)
IPv4 Address: 192.168.192.13(Preferred)
Subnet Mask: 255.255.255.0
Lease Obtained: Monday, April 1, 2024 10:12:40 AM
Lease Expires: Tuesday, April 2, 2024 10:14:28 AM
Default Gateway: fe80 :: XXXX: XXXX:XXXX:5c76%3
192.168.192.1
DHCP Server: 192.168.192.1
DHCPv6 IAID: 123527365
DHCPv6 Client DUID: 00-01-00-01-1D-AA-AD-09-64-00-6A-2B-9F-50
DNS Servers: 2001:1998:f00:1 :: 1
2001:1998: f00:2 :: 1
192.168.192.1
NetBIOS over Tcpip: Disabled
Connection-specific DNS Suffix Search List:
search.charter.net

** Deleted information **

C:\WINDOWS\system32>
C:\WINDOWS\system32>
C:\WINDOWS\system32>nslookup
Default Server: dns-cac-1b-01.rr.com
Address: 2001:1998:f00:1 :: 1

pi.hole
Server: dns-cac-1b-01.rr.com
2001:1998:f00:1 :: 1

Address:
*** dns-cac-lb-01.rr.com can't find pi.hole: Non-existent domain

server 192.168.192.1
Default Server: [192.168.192.1]
Address: 192.168.192.1
pi.hole
[192.168.192.1]
192.168.192.1

pi.hole
Addresses: fd9d:55c2:ffdb: a98:xxxx:xxxx:xxxx:xxxx
192.168.192.3

exit
C:\WINDOWS\system32>
C:\WINDOWS\system32>

Copy link

github-actions bot commented May 2, 2024

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.

@github-actions github-actions bot added the stale label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants