You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My blocky instance is accessible locally using a local IP as well as globally at a public IPv4 address. For local queries blocky can figure out the client name by querying my DHCP provider (dnsmasq). But my local DHCP provider will not answer PTR queries for public IPs. Also, reverse lookups for public IPs are not reliable anyways.
Instead, I would like the client_name of any public IP to simply be "public" or another placeholder. This would allow me to define a client group and attach allow/blocklist accordingly. For example, a public client shouldn't be able to resolve *.local or *.lan domains.
To my knowledge I can not add a wildcard/catch-all PTR record in dnsmasq
I can not specify CIDRs in the static client lookup configuration
I can specify CIDRs as a client group, but that would mean creating ~40 individual groups to match all public IPs
I could proxy/dnat the incoming traffic through one known private IP, but then blocky would not see the real source IP
Any creative solutions you can think of? Currently, I am running a patched version of blocky for this purpose. Is that something that might be useful as an upstream contribution?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
My blocky instance is accessible locally using a local IP as well as globally at a public IPv4 address. For local queries blocky can figure out the client name by querying my DHCP provider (dnsmasq). But my local DHCP provider will not answer PTR queries for public IPs. Also, reverse lookups for public IPs are not reliable anyways.
Instead, I would like the client_name of any public IP to simply be "public" or another placeholder. This would allow me to define a client group and attach allow/blocklist accordingly. For example, a public client shouldn't be able to resolve *.local or *.lan domains.
Any creative solutions you can think of? Currently, I am running a patched version of blocky for this purpose. Is that something that might be useful as an upstream contribution?
All reactions