Client 192.168.1.254 has been rate-limited (current config allows up to 1000 queries in 60 seconds)

It is manual configured (IPv4)

pi@Pi-hole:~ $ nmcli -t -f name con show --active | xargs -d '\n' -n 1 nmcli -p -f ipv4.method,ipv4.dns,ipv6.method,ipv6.dns connection show
===============================================================================
                       Connection profile details (eth0)
===============================================================================
ipv4.method:                            manual
-------------------------------------------------------------------------------
ipv4.dns:                               --
-------------------------------------------------------------------------------
ipv6.method:                            auto
-------------------------------------------------------------------------------
ipv6.dns:                               --
-------------------------------------------------------------------------------
===============================================================================
                       Connection profile details (wg0)
===============================================================================
ipv4.method:                            manual
-------------------------------------------------------------------------------
ipv4.dns:                               --
-------------------------------------------------------------------------------
ipv6.method:                            disabled
-------------------------------------------------------------------------------
ipv6.dns:                               --
-------------------------------------------------------------------------------
pi@Pi-hole:~ $

I added pi-holes address as DNS-server and set IPV6 to disabled:

pi@Pi-hole:~ $ nmcli -t -f name con show --active | xargs -d '\n' -n 1 nmcli -p -f ipv4.method,ipv4.dns,ipv6.method,ipv6.dns connection show
===============================================================================
                       Connection profile details (eth0)
===============================================================================
ipv4.method:                            manual
-------------------------------------------------------------------------------
ipv4.dns:                               192.168.1.111
-------------------------------------------------------------------------------
ipv6.method:                            disabled
-------------------------------------------------------------------------------
ipv6.dns:                               --
-------------------------------------------------------------------------------
===============================================================================
                       Connection profile details (wg0)
===============================================================================
ipv4.method:                            manual
-------------------------------------------------------------------------------
ipv4.dns:                               --
-------------------------------------------------------------------------------
ipv6.method:                            disabled
-------------------------------------------------------------------------------
ipv6.dns:                               --
-------------------------------------------------------------------------------
pi@Pi-hole:~ $
pi@Pi-hole:~ $ sudo nft list ruleset
table ip filter {
	chain INPUT {
		type filter hook input priority filter; policy accept;
		iifname "eth0" meta l4proto udp udp dport 51820  counter packets 4223 bytes 1131768 accept
		iifname "wg0" meta l4proto udp udp dport 53  counter packets 66 bytes 4847 accept
	}

	chain FORWARD {
		type filter hook forward priority filter; policy accept;
	}

	chain OUTPUT {
		type filter hook output priority filter; policy accept;
	}
}
table ip nat {
	chain PREROUTING {
		type nat hook prerouting priority dstnat; policy accept;
	}

	chain INPUT {
		type nat hook input priority 100; policy accept;
	}

	chain OUTPUT {
		type nat hook output priority -100; policy accept;
	}

	chain POSTROUTING {
		type nat hook postrouting priority srcnat; policy accept;
		oifname "eth0" ip saddr 10.210.160.0/24  counter packets 79 bytes 10948 masquerade 
	}
}
pi@Pi-hole:~ $
pi@Pi-hole:~ $ nslookup -class=chaos -type=txt version.bind 192.168.1.111
Server:		192.168.1.111
Address:	192.168.1.111#53

Non-authoritative answer:
*** Can't find version.bind: No answer

Authoritative answers can be found from:

pi@Pi-hole:~ $
pi@Pi-hole:~ $ nslookup pi.hole 192.168.1.111

Server:		192.168.1.111
Address:	192.168.1.111#53

Name:	pi.hole
Address: 192.168.1.111

pi@Pi-hole:~ $
user@MacBookAir ~ % nslookup -class=chaos -type=txt version.bind 192.168.1.111


Server:		192.168.1.111
Address:	192.168.1.111#53

Non-authoritative answer:
*** Can't find version.bind: No answer

Authoritative answers can be found from:

user@MacBookAir ~ %
user@MacBookAir ~ % nslookup pi.hole 192.168.1.111


Server:		192.168.1.111
Address:	192.168.1.111#53

Name:	pi.hole
Address: 192.168.1.111

user@MacBookAir ~ %

I do see at the moment when I hit enter after the command on my MacBookAir via VPN nslookup -class=chaos -type=txt version.bind 192.168.1.111 the following: Jan 7 07:54:52: gravity blocked version.bind is NODATA

and after the command nslookup pi.hole 192.168.1.111

Jan  7 07:55:46: query[A] pi.hole from 10.210.160.4
Jan  7 07:55:46: Pi-hole hostname pi.hole is 192.168.1.111

And from/on the Pi-Hole itself:
nslookup pi.hole 192.168.1.111

Jan  7 07:57:55: query[A] pi.hole from 192.168.1.111
Jan  7 07:57:55: Pi-hole hostname pi.hole is 192.168.1.111
Jan  7 07:57:55: query[AAAA] pi.hole from 192.168.1.111
Jan  7 07:57:55: Pi-hole hostname pi.hole is NODATA

nslookup -class=chaos -type=txt version.bind 192.168.1.111

Jan  7 07:59:21: query[TXT] version.bind from 192.168.1.111
Jan  7 07:59:21: gravity blocked version.bind is NODATA

So yes, that seems to work?

pihole -d works again :slight_smile:

Your debug token is: https://tricorder.pi-hole.net/oUQKGEs3/