immi803
Senior Member
@Martineau
How can i try unbound_manager v3.20 beta?
How can i try unbound_manager v3.20 beta?
Unfortunately, by default unbound receives DNS requests from dnsmasq, (rather than individual LAN devices) so the source IP will always be 127.0.0.1.
e.g. an unidentified LAN device is requesting a blocked ('always_nxdomain') domain 'ipid.shat.net'
If you need to have unbound report the actual IP of the LAN device then you will need to disable dnsmasq
Use 'Advanced' command 'dnsmasq disable'
e.g. unbound log will now identify/disclose LAN device 10.88.8.120 is requesting blocked ('always_nxdomain') domain 'ipid.shat.net'
Issue command@Martineau
How can i try unbound_manager v3.20 beta?
unbound_manager update=uf dev
curl --retry 3 "https://raw.githubusercontent.com/MartineauUK/Unbound-Asuswrt-Merlin/dev/unbound_manager.sh" -o "/jffs/addons/unbound/unbound_manager.sh"
If you wish to scan all of the file's contents, why waste time/effort/typing by loading two utilities...I am using the command
Code:tail -f /opt/var/lib/unbound/unbound.log | grep -i "nxdomain" tail -f /opt/var/lib/unbound/unbound.log | grep -iE "nxdomain.*192.168.1.27"
grep -i "nxdomain" /opt/var/lib/unbound/unbound.log
grep -iE "nxdomain.*192.168.1.27" /opt/var/lib/unbound/unbound.log
dnsmasq is a mature feature-rich inherent component of Asus routers.Q: What are the disadvantages of disabling dnsmasq?
- I do not use Diversion or X3MRouting.
- I do have a few static IP addresses assigned by MAC address.
- I also run WireGuard as a server on the router
Will I lose anything by keeping dsnmasq permanently disabled and letting unbound manage the same?
If you wish to scan all of the file's contents, why waste time/effort/typing by loading two utilities...
Code:grep -i "nxdomain" /opt/var/lib/unbound/unbound.log grep -iE "nxdomain.*192.168.1.27" /opt/var/lib/unbound/unbound.log
tail -f /opt/var/lib/unbound/unbound.log | grep --color="auto" -i "always_nxdomain"
So we are set to disable dnsmasq in models like ax88u? Considering performance utmost?If you wish to scan all of the file's contents, why waste time/effort/typing by loading two utilities...
Code:grep -i "nxdomain" /opt/var/lib/unbound/unbound.log grep -iE "nxdomain.*192.168.1.27" /opt/var/lib/unbound/unbound.log
dnsmasq is a mature feature-rich inherent component of Asus routers.
Consequently there is a lot of knowledge/support available in the forums for fully exploiting dnsmasq's unique features etc., and it will take time for the number of knowledgeable unbound adopters to achieve the same level of tech-savvy critical mass.
i.e. although unbound v1.11.0 may now include an 'ipset' module (only HND-model routers?), I don't think it replicates the same functionality as dnsmasq's 'ipset=' directive, but even if you don't currently use X3MRouting, you may find that the feature may be useful outside of X3MRouting.
Performance-wise, DNS resolution for clients must be a few microseconds quicker by virtue of the fact that the LAN clients don't have to go thru dnsmasq i.e. bypassing the middleman.
I personally haven't noticed any issues with disabling dnsmasq, but unbound_manager's 'dnsmasq disable' migration feature may still be limited in its abilities in advanced dnsmasq case scenarios.
YMMV
local-zone: "cn" always_nxdomain
Whoops .....one day I will learn to code.@Martineau If I am running v3.20 beta the vpn 5 command does not work and returns VPN Client arg '5' invalid, must be in range 1-5. vpn disable works as expected. I can add the vpn by reverting to the current version, running vpn 5 and then re-loading the beta.
You're doing a great job! If it helps you, you are further along than me but I can make a mean batch file for ya.Whoops .....one day I will learn to code.
I have uploaded v3.20b2 to the Github dev branch.
My configuration is similar to yours and I have the same results. After reading this entire thread, it seems some people actually see their VPN interface IP as the reported DNS server (rather than the WAN interface IP) when Accept DNS = Disabled for devices using the VPN. My knowledge here is very limited, but I believe it is working properly for us even though the various sites such as browserleaks.com or dnsleaktest.com show the WAN IP. Testing this from a client using the VPN tunnel, "nslookup whatever.com <WAN IP>" fails for me even though dnsleaktest reports this WAN IP as my DNS server. "Nslookup whatever.com <VPN IP>" works as hoped (again, even though dnsleaktest reports WAN IP as DNS server). Tenta https://tenta.com/test/ uses a different approach (try with all of your scenarios) and is unable to determine DNS server for VPN bound clients.I am confused about what should happen when routing DNS requests though a VPN
1. What DNS server should be visible for a device NOT using the VPN
2. What DNS server should be visible for a device using the VPN
Using bowserleaks.com/ip to check for the DNS address.
Enable DNS-based Filtering = Router
unbound set to use VPN 5
On the VPN 5, I set Policy Rules = Strict (with a list of devices using the VPN) and tested with both Accept DNS = Exclusive and Disabled
If Accept DNS = Exclusive then
Device not using VPN: DNS = Router IP address
Device using VPN: DNS = VPN assigned IP address
If Accept DNS = Disabled then
Device not using VPN: DNS = Router IP address
Device using VPN: DNS = Router assigned IP address
Is this what I should expect?
I agree with @QuikSilver! I have been "wrestling" with Unbound on a Raspberry Pi running Raspbian. Can't tell you how many times I wished unbound_manager was supported in the Pi...You're doing a great job! If it helps you, you are further along than me but I can make a mean batch file for ya.
unbound_manager v3.20 should not have altered the core functionality of unbound.Since updating to v3.20, I'm no longer validating DNSSEC. Completed a new build, same result. Anyone else seeing this?
Since updating to v3.20, I'm no longer validating DNSSEC. Completed a new build, same result. Anyone else seeing this?
unbound_manager v3.20 should not have altered the core functionality of unbound.
Do you have the Rootcanary DNSSEC test failure when using unbound_manager v3.19?
What are the other 4 tools you used for validation? Would you mind listing these here please?It appears that this is specific to Rootcanary. When using other validation tools (four total), I get successful validation.
My apologies to Martineau for taking up your valuable time. Thank you for what you do. You rock!
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!