What's new

Unbound unbound_manager (Manager/Installer utility for unbound - Recursive DNS Server)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

For me when changing settings like DoT or anything else and restarting unbound has caused issues or problematic test results.
OK, thank you. I'm just really curious what is happening because I see no difference in logs or in any test, which contradicts the general consensus about the DOT setting.
 
I'm at work so I cannot check at the moment, but after installing Unbound on Sunday, I was unable to access usaa.com. I didn't have a chance to do any troubleshooting but if someone can check to see if they can access it, then I'll know it's a setup issue on my end.
Here is my unbound test

1. Enable logging
2. Enable scribe
3. Set 'verbosity: 4' (No doubt overkill)
4. Browse to usaa.com

unbound debug log for usaa.com

The website usaa.com opened correctly for me, but if you were to follow the same (debugging) process, would a (crude but simple) 'diff' with my results file identify how/why/where unbound fails?
 
Well, after browsing as I said (L&LD) the percentage has risen to 61% I do not know if it will be correct.
 
OK, thank you. I'm just really curious what is happening because I see no difference in logs or in any test, which contradicts the general consensus about the DOT setting.
Ok I made some tests again, and I still think that DOT settings in the GUI doesn't matter. Maybe turning it off saves some RAM(?), but that is all I can see.
 
I sympathise, but without a knowledgeable SME to provide a tutorial regarding what information can be extracted/inferred from increasing the 'verbosity: X' directive or alternatively using 'dig', then identifying your unbound issues may take a while.

However, if you posted the 'dig' output for a domain that inexplicably fails, together with the section of the 'unbound.log' (having temporarily increased 'verbosity: X') then there may be clue in the output.

unbound is definitely a new technology for probably 99% of us, but I suspect that if the same spurious issues occurred with say dnsmasq+DoT+DNSSEC etc., would it be straight forward to instantly identify the reason?

I couldn't help myself and did some more digging. Here is the output from unbound.log after a failed attempt to access fudzilla.com:

Feb 11 16:34:29 unbound[22548:0] query: 127.0.0.1 www.fudzilla.com. A IN
Feb 11 16:34:29 unbound[22548:0] error: SERVFAIL <ns.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:29 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:29 unbound[22548:0] query: 127.0.0.1 www.fudzilla.com. A IN
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. AAAA IN>: SERVFAIL in cache
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <www.fudzilla.com. A IN>: all servers for this domain failed, at zone fudzilla.com.
Feb 11 16:34:30 unbound[22548:0] reply: 127.0.0.1 www.fudzilla.com. A IN SERVFAIL 0.584118 0 34
Feb 11 16:34:30 unbound[22548:0] reply: 127.0.0.1 www.fudzilla.com. A IN SERVFAIL 1.035926 0 34

NSLOOKUP for fudzilla.com
Server: 1.1.1.1
Address 1: 1.1.1.1 one.one.one.one

Name: fudzilla.com
Address 1: 185.203.18.82 fudzilla.com
 
Ok I made some tests again, and I still think that DOT settings in the GUI doesn't matter. Maybe turning it off saves some RAM(?), but that is all I can see.
The unbound changes made to dnsmasq via the dnsmasq.postconf/unbound.postconf scripts will "detach" dnsmasq from stubby, so you are better off disabling DNS Privacy (DoT) in the GUI to save memory.
 
I couldn't help myself and did some more digging. Here is the output from unbound.log after a failed attempt to access fudzilla.com:

Feb 11 16:34:29 unbound[22548:0] query: 127.0.0.1 www.fudzilla.com. A IN
Feb 11 16:34:29 unbound[22548:0] error: SERVFAIL <ns.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:29 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:29 unbound[22548:0] query: 127.0.0.1 www.fudzilla.com. A IN
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. AAAA IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns.h3s.org. AAAA IN>: SERVFAIL in cache
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <ns2.h3s.org. A IN>: all servers for this domain failed, at zone h3s.org.
Feb 11 16:34:30 unbound[22548:0] error: SERVFAIL <www.fudzilla.com. A IN>: all servers for this domain failed, at zone fudzilla.com.
Feb 11 16:34:30 unbound[22548:0] reply: 127.0.0.1 www.fudzilla.com. A IN SERVFAIL 0.584118 0 34
Feb 11 16:34:30 unbound[22548:0] reply: 127.0.0.1 www.fudzilla.com. A IN SERVFAIL 1.035926 0 34

NSLOOKUP for fudzilla.com
Server: 1.1.1.1
Address 1: 1.1.1.1 one.one.one.one

Name: fudzilla.com
Address 1: 185.203.18.82 fudzilla.com
What do you get if you run:
Code:
unbound-control dump_cache | grep h3s
 
The unbound changes made to dnsmasq via the dnsmasq.postconf/unbound.postconf scripts will "detach" dnsmasq from stubby, so you are better off disabling DNS Privacy (DoT) in the GUI to save memory.
Thanks for the clarification, indeed, more memory is better.
All I was trying to say that the DOT settings in the GUI won't really cause DNS problems when using unbound (unless such problems would happen because of low memory).
 
What do you get if you run:
Code:
unbound-control dump_cache | grep h3s
RT-AX88U-5BD0:/tmp/home/root# unbound-control dump_cache | grep h3s
ns2.h3s.org. 19545 IN AAAA \# 0
ns2.h3s.org. 19545 IN A 185.203.18.38
ns2.h3s.org. 19544 IN A 185.203.18.38
h3s.org. 19544 IN NS ns2.h3s.org.
h3s.org. 19544 IN NS ns.h3s.org.
fudzilla.com. 19544 IN NS ns.h3s.org.
fudzilla.com. 19544 IN NS ns2.h3s.org.
GSBJ5GR56BVMLLGB5S15KO3G1SPRN9CK.net. 19713 IN NSEC3 1 1 0 - gsc32e1k1me26fh3s0bbfavooh1m5khg NS DS RRSIG ;{flags: optout}
ns.h3s.org. 19545 IN AAAA \# 0
ns.h3s.org. 19545 IN A 185.203.18.38
ns.h3s.org. 19544 IN A 185.203.18.38
fudzilla.com. 19551 IN NS ns.h3s.org.
fudzilla.com. 19551 IN NS ns2.h3s.org.
h3s.org. 19551 IN NS ns2.h3s.org.
h3s.org. 19551 IN NS ns.h3s.org.
 
RT-AX88U-5BD0:/tmp/home/root# unbound-control dump_cache | grep h3s
ns2.h3s.org. 19545 IN AAAA \# 0
ns2.h3s.org. 19545 IN A 185.203.18.38
ns2.h3s.org. 19544 IN A 185.203.18.38
h3s.org. 19544 IN NS ns2.h3s.org.
h3s.org. 19544 IN NS ns.h3s.org.
fudzilla.com. 19544 IN NS ns.h3s.org.
fudzilla.com. 19544 IN NS ns2.h3s.org.
GSBJ5GR56BVMLLGB5S15KO3G1SPRN9CK.net. 19713 IN NSEC3 1 1 0 - gsc32e1k1me26fh3s0bbfavooh1m5khg NS DS RRSIG ;{flags: optout}
ns.h3s.org. 19545 IN AAAA \# 0
ns.h3s.org. 19545 IN A 185.203.18.38
ns.h3s.org. 19544 IN A 185.203.18.38
fudzilla.com. 19551 IN NS ns.h3s.org.
fudzilla.com. 19551 IN NS ns2.h3s.org.
h3s.org. 19551 IN NS ns2.h3s.org.
h3s.org. 19551 IN NS ns.h3s.org.
Can you ping that 185 address?
 
No, doesn't work from the router:
RT-AX88U-5BD0:/tmp/home/root# ping 185.203.18.38
PING 185.203.18.38 (185.203.18.38): 56 data bytes
ping: sendto: Operation not permitted
 
No, doesn't work from the router:
RT-AX88U-5BD0:/tmp/home/root# ping 185.203.18.38
PING 185.203.18.38 (185.203.18.38): 56 data bytes
ping: sendto: Operation not permitted
Check if Skynet is blocking anything, perhaps a country ban (e.g. Croatia)?
Code:
firewall stats search ip 185.203.18.38
 
It would be interesting to know if the people having issues also use country bans in Skynet. Since there is no single DNS server that the router talks to, it isn't possible for Skynet to whitelist all possible DNS servers that Unbound may need to talk to. Although I wonder if there's any harm in whitelisting port 53 outbound (not currently possible in Skynet).
 
Great work on this script Martineau and everyone. Installed, updated and works, cache at 68%. I notice that <Enable local NTP server> keeps reverting back to NO, any problems with that? And, if I reboot does the unbound cache get cleared, if so anyway to preserve it through reboots?
 
I uninstalled unbound with unbound_manager and rebooted.
I redownloaded the script with amtm and installed unbound_manager with all defaults.
I enabled logging.
I enabled scribe
I set verbosity to 4.

With Chrome, I navigated to usaa.com. It loaded fine.
I refreshed the page, and got the blank page: A brief flash of the top of the blue banner and then all white.

With Firefox, I navigated to usaa.com and it loaded fine. I reloaded the page several times. I closed Firefox and then reloaded the page fine; Chrome still blank. I closed Firefox again, reloaded the page, and got a blank: same flash and white.

I ran a diff between my log file and yours, and they are completely different from the get-go but it doesn't seem to be a fail:
Code:
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 usaa.com. A IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 usaa.com. A IN NOERROR 0.000000 1 42
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 usaa.com. A IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 usaa.com. A IN NOERROR 0.000000 1 42
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 usaa.com. A IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 usaa.com. A IN NOERROR 0.000000 1 42
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 usaa.com. AAAA IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 usaa.com. AAAA IN NOERROR 0.000000 1 79
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 www.usaa.com. A IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 www.usaa.com. A IN NOERROR 0.000000 1 119
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 www.usaa.com. A IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 www.usaa.com. A IN NOERROR 0.000000 1 119
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e6962.b.akamaiedge.net. A IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e6962.b.akamaiedge.net. A IN NOERROR 0.008633 0 56
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e6962.b.akamaiedge.net. AAAA IN
Feb 11 16:49:00 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e6962.b.akamaiedge.net. AAAA IN NOERROR 0.000000 1 101
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 content.usaa.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 content.usaa.com. A IN NOERROR 0.000000 1 123
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 s.go-mpulse.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 s.go-mpulse.net. AAAA IN NOERROR 0.000000 1 172
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 mboxedge17.tt.omtrdc.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 mboxedge17.tt.omtrdc.net. AAAA IN NOERROR 0.000000 1 111
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 api.usaa.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 api.usaa.com. A IN NOERROR 0.000000 1 119
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 api.usaa.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 api.usaa.com. A IN NOERROR 0.000000 1 119
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e6968.b.akamaiedge.net. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e6968.b.akamaiedge.net. A IN NOERROR 0.011016 0 56
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e6968.b.akamaiedge.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e6968.b.akamaiedge.net. AAAA IN NOERROR 0.000000 1 101
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 c.go-mpulse.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 c.go-mpulse.net. AAAA IN NOERROR 0.000000 1 200
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 tms.usaa.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 tms.usaa.com. A IN NOERROR 0.000000 1 119
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 tms.usaa.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 tms.usaa.com. A IN NOERROR 0.000000 1 119
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e7059.x.akamaiedge.net. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 tags.tiqcdn.com. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 tags.tiqcdn.com. AAAA IN NOERROR 0.000000 1 123
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e7059.x.akamaiedge.net. A IN NOERROR 0.011858 0 56
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e7059.x.akamaiedge.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e7059.x.akamaiedge.net. AAAA IN NOERROR 0.000000 1 101
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 dpm.demdex.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 dpm.demdex.net. AAAA IN NOERROR 0.000000 1 222
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 www.everestjs.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 www.everestjs.net. AAAA IN NOERROR 0.000000 1 169

Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 da.usaa.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 da.usaa.com. A IN NOERROR 0.000000 1 118
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 dcs-edge-va6-802167536.us-east-1.elb.amazonaws.com. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 dcs-edge-va6-802167536.us-east-1.elb.amazonaws.com. AAAA IN NOERROR 0.000000 0 150
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 scontent.xx.fbcdn.net. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 scontent.xx.fbcdn.net. A IN NOERROR 0.025262 0 55
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 scontent.xx.fbcdn.net. A IN NOERROR 0.051173 0 55
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 scontent.xx.fbcdn.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 scontent.xx.fbcdn.net. AAAA IN NOERROR 0.000000 1 67
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 gb.usaa360.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 gb.usaa360.com. A IN NOERROR 0.000000 1 121
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 gb.usaa360.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 gb.usaa360.com. A IN NOERROR 0.000000 1 121
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e8561.x.akamaiedge.net. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e8561.x.akamaiedge.net. A IN NOERROR 0.013634 0 56
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e8561.x.akamaiedge.net. AAAA IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e8561.x.akamaiedge.net. AAAA IN NOERROR 0.000000 1 101
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] query: 127.0.0.1 gb.usaa360.com. A IN
Feb 11 16:49:01 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 gb.usaa360.com. A IN NOERROR 0.000000 1 121

Feb 11 16:49:04 RT-AC86U unbound: [32101:0] query: 127.0.0.1 localhost. SSHFP IN
Feb 11 16:49:04 RT-AC86U unbound: [32101:0] info: localhost. redirect 127.0.0.1@46630 localhost. SSHFP IN
Feb 11 16:49:04 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 localhost. SSHFP IN NOERROR 0.000000 1 88
Feb 11 16:49:04 RT-AC86U unbound: [32101:0] query: 127.0.0.1 localhost. SSHFP IN
Feb 11 16:49:04 RT-AC86U unbound: [32101:0] info: localhost. redirect 127.0.0.1@55083 localhost. SSHFP IN
Feb 11 16:49:04 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 localhost. SSHFP IN NOERROR 0.000000 1 88
Feb 11 16:49:11 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e8561.x.akamaiedge.net. AAAA IN
Feb 11 16:49:11 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e8561.x.akamaiedge.net. AAAA IN NOERROR 0.000000 1 101
Feb 11 16:49:11 RT-AC86U unbound: [32101:0] query: 127.0.0.1 l.usaa.com. A IN
Feb 11 16:49:11 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 l.usaa.com. A IN NOERROR 0.000000 1 117
Feb 11 16:49:11 RT-AC86U unbound: [32101:0] query: 127.0.0.1 e6962.b.akamaiedge.net. AAAA IN
Feb 11 16:49:11 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 e6962.b.akamaiedge.net. AAAA IN NOERROR 0.000000 1 101
Feb 11 16:49:12 RT-AC86U unbound: [32101:0] query: 127.0.0.1 mtalk.google.com. A IN
Feb 11 16:49:12 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 mtalk.google.com. A IN NOERROR 0.000000 1 79
Feb 11 16:49:18 RT-AC86U unbound: [32101:0] query: 127.0.0.1 17.client-channel.google.com. A IN
Feb 11 16:49:18 RT-AC86U unbound: [32101:0] reply: 127.0.0.1 17.client-channel.google.com. A IN NOERROR 0.000000 1 62
 
Great work on this script Martineau and everyone. Installed, updated and works, cache at 68%. I notice that <Enable local NTP server> keeps reverting back to NO, any problems with that? And, if I reboot does the unbound cache get cleared, if so anyway to preserve it through reboots?
There's a script on the Unbound repo from NLNet Labs that will dump and load the cache. It would need to be adapted for the Entware paths. It's only useful if the time between the dump and the load is short. Otherwise, you might be loading back something that was meant to expire.

https://github.com/NLnetLabs/unbound/blob/master/contrib/unbound_cache.sh
 
So it is blocked.
Now I'm confused. When unbound is off I can access the website even though it's blocked in Skynet. When unbound is on it's blocked.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top