Menu
What's new
By:
Filters Better Search

Search results

  • 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!

  1. SolluxCaptor

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

    Yes I tried that way, and also simply ran "sgui", after doing another removal of Unbound (and reboot) which automatically enabled stats+ first according to terminal output. Correct, all but the bottom general statistics are empty or say "No data to display" Calculated Cache Hit Percentage...
  2. SolluxCaptor

    "I am the Conductor."

    "I am the Conductor."
  3. SolluxCaptor

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

    Is anyone else having issues with the GUI? Ran sgui command after fresh installation (384.15) and even after a couple days I see "no data" in all graph areas and some just plain blank. All I get is the very bottom statistic. Running the command to show those extra stats in the terminal work just...
  4. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Aha! That's perfect, thanks :D
  5. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    https://www.isc.org/docs/matthijs-mekking-oarc30-unsupported-algorithms.pdf Edit: better link - https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xml
  6. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Someone feel free to correct me if I am wrong on this, but wasn't DSA depreciated in DNSSEC? Edit: better link https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xml
  7. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Excellent. Also, I was curious, how can we see the parameters which Entware packages were compiled? For example, how can I check if Unbound was compiled (this time) with Libevent support?
  8. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    DOH. Meant 1.9.3 :p corrected
  9. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Hopefully we hear from him shortly, but I believe he means with Unbound 1.9.6 the default .conf file is different than we had prior to the Entware update - we were stuck with 1.9.3 before which had a different base config. I noticed that as well - but not sure if that is what he meant...
  10. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    I'm sorry to see you go like this, but I think I speak for all here that we are very grateful for your contribution, and bringing this idea of Unbound + Merlin FW to life (even with help of others)! It is a real pain to have gotten even this far I am sure. I hope to see you back on in the...
  11. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    I know you don't need my opinion - but I completely agree with you. Throughout the project I was noticing occasionally an update changed my .conf file and added / changed these parameters. I did not have the time then to look into them, but wrongly assumed they must be helpful - it would be...
  12. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Just a heads up - it looks like we got an Entware package update to Unbound 1.9.6 today! Run AMTM and U to update packages. Fantastic news, closes remaining security holes and brings us up to date!
  13. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Same exact issue as above FWIW. Appears to work regardless, but seeing many repeated messages during update (same messages as described above).
  14. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Unbound does provide IPV6 support. But if you want to disable it you can in the config file. You can edit it by running:unbound_manager and: vx to edit Unbound's config quickly. Look for do-ip6: yes and change to no. The main thing to look out for is to disable the feature in the router to...
  15. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Correct me if I'm wrong, but doesn't using DoT actually leave its own form of trail behind on those DNS servers? If I recall it was due to the nature of TLS. The connection is more secure, but it leaves a bit of a paper trail on the DoT server, I think due to handshakes. Granted, it is only...
  16. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    Another thing of note, your ISP will most likely still be able to see your history based on IP once you complete the DoT protocol. Once you get the destionation IP back from the DoT server - then its all pure IP traffic to your ISP (as usual) - and if they perform any Deep Packet Inspection, or...
  17. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    It depends, for me I was seeing over 300ms for initial lookups (before caching) with Stubby using Cloudflare DoH. But once cached, you will get 1ms DNS response as normal for Unbound. For reference, without Stubby I see about 30ms (normally) to 268ms (with 268 being from another country)...
  18. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    I was noticing most of it was buffer / disk cache as Linux does. Lol but reboot clears it back to about 76% for a while, but over time it grows! And seriously, just insanity how fast we're getting :D:D
  19. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    I had it set to 3600 when I got that high TTL though.. I am trying to say that option may bypass that timeout if set to yes, if I read its English correctly. In any case we can only test [emoji106]
  20. SolluxCaptor

    Unbound - Authoritative Recursive Caching DNS Server

    This is the part I am not understanding I think: If it fails to retrieve it upstream? This makes it sound permanent if always requested - always a TTL expired cached response. - not sure if it means until Unbound's set TTL value though? It may just be me though, lol - but I was seeing over 2k...
Top