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
For personal use i've implemented a plugin to enable client based forwarding. Been using it for months without issue. Was wondering if it is useful to anyone else. Note, this is NOT the same as domain based selective upstream forwarding but client source IP based forwarding
Use case:
I have at home TV and Nvidia sheild which i want to route thru different upstream servers, but for the rest of the house (with kids) i want to route DNS requests to child friendly resolvers and for me and my wife i want to just route DNS request to adblocked resolvers.
in the .toml file and the forwarding rules (client-forwarding-rules.txt) are like
10.0.0.50,10.0.0.20 1.1.1.1
10.0.0.30 8.8.8.8
All the other clients/networks will get subjected to the other default resolving rules.
I am using this on a openwrt x86 router. It must be the first in the resolving chain of course as it get the client IP source address to decide where to route the DNS request to. So dnsmasq needs to be disabled or moved to a secondary (non 53) port first so this becomes the primary resolver, and then for lan resolution (since DHCP is provided by dnsmasq) you can use the forwarding-rules.txt to provide .lan and .in-addr.arpa resolution.
Do you think this is worth submitting for wider use, or my use case is too narrow (i.e. me only). The plugin code is extremely simple just a few lines and took me all of 1/2hr to implement - probably more of a indication of the lovely codebase and language than my skills.
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
-
Hi all,
For personal use i've implemented a plugin to enable client based forwarding. Been using it for months without issue. Was wondering if it is useful to anyone else. Note, this is NOT the same as domain based selective upstream forwarding but client source IP based forwarding
Use case:
I have at home TV and Nvidia sheild which i want to route thru different upstream servers, but for the rest of the house (with kids) i want to route DNS requests to child friendly resolvers and for me and my wife i want to just route DNS request to adblocked resolvers.
So the plugin just adds section
in the .toml file and the forwarding rules (client-forwarding-rules.txt) are like
All the other clients/networks will get subjected to the other default resolving rules.
I am using this on a openwrt x86 router. It must be the first in the resolving chain of course as it get the client IP source address to decide where to route the DNS request to. So dnsmasq needs to be disabled or moved to a secondary (non 53) port first so this becomes the primary resolver, and then for lan resolution (since DHCP is provided by dnsmasq) you can use the forwarding-rules.txt to provide .lan and .in-addr.arpa resolution.
Do you think this is worth submitting for wider use, or my use case is too narrow (i.e. me only). The plugin code is extremely simple just a few lines and took me all of 1/2hr to implement - probably more of a indication of the lovely codebase and language than my skills.
Beta Was this translation helpful? Give feedback.
All reactions